EastCoasthandle
New Member
- Joined
- Apr 21, 2005
- Messages
- 6,885 (0.94/day)
| System Name | MY PC |
|---|---|
| Processor | E8400 @ 3.80Ghz > Q9650 3.60Ghz |
| Motherboard | Maximus Formula |
| Cooling | D5, 7/16" ID Tubing, Maze4 with Fuzion CPU WB |
| Memory | XMS 8500C5D @ 1066MHz |
| Video Card(s) | HD 2900 XT 858/900 to 4870 to 5870 (Keep Vreg area clean) |
| Storage | 2 |
| Display(s) | 24" |
| Case | P180 |
| Audio Device(s) | X-fi Plantinum |
| Power Supply | Silencer 750 |
| Software | XP Pro SP3 to Windows 7 |
| Benchmark Scores | This varies from one driver to another. |
If you've been using older version of Driver Sweeper you have problems installing SP1. What you need to do is type CMD with admin rights and type: sfc /scannow. Once 100% completed if there are no errors then you can stop here. You shouldn't have any problems with SP1. If there are problems goto windows\logs\cbs.log and see if you find any of the following:
Option 1 Driver Sweeper Repair
If the above problems are found there is a partial fix for it (the above includes both missing ATI and Nvidia manifest and other OS components). The admin for Driver Sweeper has provided a method to restoring the missing ATI manifests/directories that were accidentally deleted. Please visit his forum here for detail instructions on what to do. Once done you should open up CMD using admin priv. and do a sfc /scannow. Keep in mind that sfc may find more then just missing ati/nv manifests. So check out thecbs.log for information of what's going on. Look for "invalid", "damage" "missing" or "false" as a word search to narrow down the problem. You can look at CheckSUR.log for any errors you find (thanks to xsever for the info).
Option 2 MS's System Update Readiness Tool
x86
Option 3 (if this isn't for you just do a restore or a upgrade install=repair)
This method is a bit more convoluted and cumbersome if you don't have the nv*.* mainfest/directories.
The link mentioned earlier will restore all ATI related manifests/files, etc only. If the SFC.exe check reveals that the NV*.* manifest/directories are missing it can be fixed and here's the general idea of how to do it. You want to extract specific manifest and directories or files from your OS install disc and place it back into your OS. When saving them on the hard drive you want to retain the exact /%SystemRoot%/subfolders so you know where each manifest/directories go. For example create the following folder using the following sub folders on your hard drive:
win\system32\DriverStore\FileRespository\
next create the subdirectories:
win\winsxs
win\winsxs\manifest
and place all the manifest/directories from the CD in the appropriate location noted above so you know where to paste them in your %SystemRoot%. Below is what you need to do:
-You need to get 7-zip goto Options then the System Tab and enable all associations.
-Then you place your OS disc in the drive. Using 7-zip navigate to Sources\install.win (a compressed file)
-Wait a few minutes then open the 1.xml file and find out which OS version you have. Each numbered folder corresponds to a different OS Type (IE:Startup, Professional, Ultimate, etc).
-Navigate to the appropriate numbered folder that corresponds to your OS type.
-Navigate to the following sub directories and copy all NV manifest/folders to a separate folder on your PC created subfolder (from earlier):
windows\system32\DriverStore\FileRespository\
windows\winsxs\
windows\winsxs\Manifests\
The name of and location of the manifest, etc are as follows (most provided by k1net1cs)
Now you need to places those manifests/directories in your installed OS's sub directories. The location is similar as written earlier:
C:\windows\system32\DriverStore\FileRespository\
C:\windows\winsxs\
C:\windows\winsxs\Manifests\
The only problem is that some may need to take ownership of:
filerespository
winsxs
Manifests
subdirectories. In that case you will need to research how to do it. Or else you will be denied access to paste those missing manifest folders/files. But if you know how and are able to paste them just reboot the PC. What will happen is that you will be pasting them in the appropriate locations without replacing any existing manifest/directories. Once done you should open up CMD using admin priv. and do a sfc /scannow to see if all is well or not. Keep in mind that sfc may find more then just missing ati/nv manifests. So check out the cbs.log for information of what's going on. Look for "invalid", "damage" "missing" or "false" as a word search to narrow down the problem.
Option 4
Just place your OS install disc in the drive and do a upgrade which is considered a repair of the OS. You won't lose your files/programs but any OS tweaks, settings, drivers and updates will be lost though.
Code:
2011-02-02 13:53:07, Info CSI 000002e2 [SR] Cannot verify component files for atiriol6.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2011-02-02 13:53:07, Info CSI 000002e3 [SR] Cannot verify component files for atiilhag.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2011-02-02 13:53:07, Info CSI 000002e4 [SR] Cannot verify component files for atiilhag.inf-LanguagePack, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2011-02-02 13:53:07, Info CSI 000002e5 [SR] Cannot verify component files for atiilhag.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2011-02-02 13:53:07, Info CSI 000002e6 [SR] Cannot verify component files for nv_lh.inf-LanguagePack, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2011-02-02 13:53:07, Info CSI 000002e7 [SR] Cannot verify component files for nv_lh.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2011-02-02 13:53:07, Info CSI 000002e8 [SR] Cannot verify component files for nv_lh.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)Option 1 Driver Sweeper Repair
If the above problems are found there is a partial fix for it (the above includes both missing ATI and Nvidia manifest and other OS components). The admin for Driver Sweeper has provided a method to restoring the missing ATI manifests/directories that were accidentally deleted. Please visit his forum here for detail instructions on what to do. Once done you should open up CMD using admin priv. and do a sfc /scannow. Keep in mind that sfc may find more then just missing ati/nv manifests. So check out the
Option 2 MS's System Update Readiness Tool
x64
x86
Option 3 (if this isn't for you just do a restore or a upgrade install=repair)
This method is a bit more convoluted and cumbersome if you don't have the nv*.* mainfest/directories.
The link mentioned earlier will restore all ATI related manifests/files, etc only. If the SFC.exe check reveals that the NV*.* manifest/directories are missing it can be fixed and here's the general idea of how to do it. You want to extract specific manifest and directories or files from your OS install disc and place it back into your OS. When saving them on the hard drive you want to retain the exact /%SystemRoot%/subfolders so you know where each manifest/directories go. For example create the following folder using the following sub folders on your hard drive:
win\system32\DriverStore\FileRespository\
next create the subdirectories:
win\winsxs
win\winsxs\manifest
and place all the manifest/directories from the CD in the appropriate location noted above so you know where to paste them in your %SystemRoot%. Below is what you need to do:
-You need to get 7-zip goto Options then the System Tab and enable all associations.
-Then you place your OS disc in the drive. Using 7-zip navigate to Sources\install.win (a compressed file)
-Wait a few minutes then open the 1.xml file and find out which OS version you have. Each numbered folder corresponds to a different OS Type (IE:Startup, Professional, Ultimate, etc).
-Navigate to the appropriate numbered folder that corresponds to your OS type.
-Navigate to the following sub directories and copy all NV manifest/folders to a separate folder on your PC created subfolder (from earlier):
windows\system32\DriverStore\FileRespository\
windows\winsxs\
windows\winsxs\Manifests\
The name of and location of the manifest, etc are as follows (most provided by k1net1cs)
- In %SystemRoot%\System32\DriverStore\FileRepository, you need :
- [dir] atiilhag.inf_amd64_* or atiilhag.inf_x86_*
- [dir] atiriol6.inf_amd64_* or atiriol6.inf_x86_*
- [dir] nv_lh.inf_amd64_* or nv_lh.inf_x86_*
- In %SystemRoot%\winsxs, you need :
- [dir] amd64_atiilhag.inf.resources_* or x86_atiihag.inf.resources_*
- [dir] amd64_atiilhag.inf_* or x86_atiihag.inf
- [dir] amd64_atiriol6.inf_* or x86_atiriol6.inf_*
- [dir] amd64_nv_lh.inf.resources_* or x86_nv_lh.inf.resources_*
- [dir] amd64_nv_lh.inf_* or x86_nv_lh.inf_*
- In %SystemRoot%\winsxs\Manifests, you need :
- [file] amd64_atiilhag.inf-languagepack_*.manifest or x86_atiihag.inf-languagepack_*.manifest
- [file] amd64_atiilhag.inf.resources_*.manifest or x86_atiihag.inf.resources_*.manifest
- [file] amd64_atiilhag.inf_*.manifest or x86_atiihag.inf_*.manifest
- [file] amd64_atiriol6.inf_*.manifest or x86_atiriol6.inf_*.manifest
- [file] amd64_nv_lh.inf-languagepack_*.manifest or x86_nv_lh.inf-languagepack_*.manifest
- [file] amd64_nv_lh.inf.resources_*.manifest or x86_nv_lh.inf.resources_*.manifest
- [file] amd64_nv_lh.inf_*.manifest or x86_nv_lh.inf_*.manifest
Now you need to places those manifests/directories in your installed OS's sub directories. The location is similar as written earlier:
C:\windows\system32\DriverStore\FileRespository\
C:\windows\winsxs\
C:\windows\winsxs\Manifests\
The only problem is that some may need to take ownership of:
filerespository
winsxs
Manifests
subdirectories. In that case you will need to research how to do it. Or else you will be denied access to paste those missing manifest folders/files. But if you know how and are able to paste them just reboot the PC. What will happen is that you will be pasting them in the appropriate locations without replacing any existing manifest/directories. Once done you should open up CMD using admin priv. and do a sfc /scannow to see if all is well or not. Keep in mind that sfc may find more then just missing ati/nv manifests. So check out the cbs.log for information of what's going on. Look for "invalid", "damage" "missing" or "false" as a word search to narrow down the problem.
Option 4
Just place your OS install disc in the drive and do a upgrade which is considered a repair of the OS. You won't lose your files/programs but any OS tweaks, settings, drivers and updates will be lost though.
Last edited:
