• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Driver Sweeper, Win7 SP1 and YOU!!

EastCoasthandle

New Member
Joined
Apr 21, 2005
Messages
6,885 (0.93/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:

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 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. 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

This tool is being offered because an inconsistency was found in the Windows servicing store which may prevent the successful installation of future updates, service packs, and software.
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:
Interesting, I got an error about the SXS manifest being corrupt during SP1 install, but a reboot and installing SP1 right after the machine booted fixed my issue.
 
This doesnt make sense. Does this only effect AMD/ATI rigs? Where did you get this info?
 
This doesn't make sense. Does this only effect AMD/ATI rigs? Where did you get this info?
The best way to determine if this is an issue for you or not (besides not being able to install SP1) is to run scannow and see what comes up. If you don't have any errors you are fine. If you do have errors and are related to the OP then follow the instructions Here. The admin over there provided a way to restore those missing manifest, etc.
 
The best way to determine if this is an issue for you or not (besides not being able to install SP1) is to run scannow and see what comes up. If you don't have any errors you are fine. If you do have errors and are related to the OP then follow the instructions Here. The admin over there provided a way to restore those missing manifest, etc.

Well as long as you used the latest driversweaper your fine.
 
Well as long as you used the latest driversweaper your fine.
Pretty much but thats with Driver Sweeper 2.8.5 or later. That's why I went through the effort to post a thread asking people to check. That version was released on January 22, 2011.
 
thank God I'm on SP 0
 
thank God I'm on SP 0

This is only an issue with the currently release SP1. If that is actually the same one that will be released later this year then some might have a problem installing it. However, they can/may alter it between now and then so that this isn't a problem. But that's just a guess on my part. SP1 from NGO is suppose to be RTM (release to manufacture) which would make it the final version. But I have no way of confirming that though.
 
I didn't know anyone still used Driver Sweeper anymore.

Also I'm with alexsubri on this one! SP0 ftw! :laugh:
 
I didn't even know SP1 was out yet..
 
There is a version of SP1 that can be downloaded but I have no way to confirm if that's the final version or not. So far, those that are using that version of SP1 had problems because some of the uninstall programs mistaken ati and nvidia manifest as part of the driver install. When they tried to install SP1 it runs integrity check of your OS. Once it comes back with a problem (because those manifest, etc were missing) it halts the install of SP1. This is were I suggest that you do a sfc /scannow from CMD prompt with admin rights before doing anything else.

Now will this happen with the final official release? Maybe/maybe not but if if you only used the older driver sweeper then this is a fairly simple fix.
 
If you never used any drive sweeper your golden.
 
If you never used any drive sweeper your golden.

Yes, but lets just say if you used any driver uninstall program use SFC to check your OS integrity.
 
Like the one AMD and nVidia include? Why would anyone use anything else?
 
Like the one AMD and nVidia include? Why would anyone use anything else?
Include? It's their own uninstall procedure. Why would you say it's included as if it's some sort of 3rd party program? It should be common knowledge by now that their own unistall of their drivers is considered part of their own uninstall process. But, just to make it clear for you I am referring to 3rd party programs.
 
Last edited:
I know, it was late and I was just having a little fun. :toast:

I just don't understand why anyone would use driver sweeper at all but that's another topic.

Do you happen to know if there is any date set yet for when SP1 is suppose to show up?
 
I know, it was late and I was just having a little fun. :toast:

I just don't understand why anyone would use driver sweeper at all but that's another topic.

Do you happen to know if there is any date set yet for when SP1 is suppose to show up?

Sounds like someone doesn't have an ATI video card to me.
 
Well not just having an ATI video card but anyone who may have had a problem in the past or switching between makers. Usually the 1st thing they like to do is look for an app that completely removes all driver remnants.
 
Well not just having an ATI video card but anyone who may have had a problem in the past or switching between makers. Usually the 1st thing they do is look for an app that completely removes all driver remnants.

Good point. Thanks for this fix by the way, my SFC is now squeaky clean.
 
Sounds like someone doesn't have an ATI video card to me.

:roll:

Been installing new drivers over old since the beginning of 2009 (with my 4870x2 at the time) without a problem. Got a couple 5870s now and still never once a problem. Also have swapped back and forth between ATI and nVidia on same system and OS all without a problem. Only problem I have is with ULPS and Afterburner.

Sooooo..........
 
:roll:

Been installing new drivers over old since the beginning of 2009 (with my 4870x2 at the time) without a problem. Got a couple 5870s now and still never once a problem. Also have swapped back and forth between ATI and nVidia on same system and OS all without a problem. Only problem I have is with ULPS and Afterburner.

Sooooo..........

You are not everyone. Ever hear of corruption? I'm not sure exactly what you are trying to prove here besides making an ass out of yourself.
 
Just so you know, SP1 was released to manufactures today and will be released to the public on 22nd of this month.
source
The 2 new features are:
Dynamic Memory for virtual machine
RemoteFX
 
I ran into this problem where I got error 80073712 when I tried to install SP1.

I will go through your suggested instructions, and report back.
 
Back
Top