Windows 7 Premium x64 upgrade to windows 10

G

ghard

New member
Joined
Feb 7, 2016
Posts
2
I tried your SFCFix and it gives me back this message that it cannot correct this corruption. Any help would be appreciated.

SFCFix version 2.4.9.2 by niemiro.
Start time: 2016-02-07 22:08:50.570
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








AutoAnalysis::
WARNING: Failed to get store name from identity name with return code 2 for component ntprint.inf and file Amd64\XPSSVCS.DLL. File is reported as corrupt by SFC.
CORRUPT: Amd64\XPSSVCS.DLL of component ntprint.inf.




CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-printing-reach_31bf3856ad364e35_6.1.7600.16385_none_82616c052be308de\xpssvcs.dll




SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 2
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 2
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-02-07 22:10:07.062
----------------------EOF-----------------------
 
I'm not entirely familiar with that tool - but I thought that it was meant for Windows 8/8.1.

Regardless, can I assume that at some point prior to the SFCfix tool, you tried the sfc /scannow command to check things, and it found but could not fix corrupted files? And that you ran the tests because your system is having trouble ... I'd be interested in what the troubles are.
 
OldGrayGary said:
I'm not entirely familiar with that tool - but I thought that it was meant for Windows 8/8.1.

Regardless, can I assume that at some point prior to the SFCfix tool, you tried the sfc /scannow command to check things, and it found but could not fix corrupted files? And that you ran the tests because your system is having trouble ... I'd be interested in what the troubles are.
Click to expand...

Yes, i ran sfc /scannow. I am not having problems with the system per se, just wont allow me to upgrade to windows 10 and reverts to prior operating system.

I ran this script i saw, and i get these errors in sfcdetails.txt:

2016-02-08 16:05:45, Info CSI 00000c06 [SR] Cannot repair member file [l:22{11}]"xpssvcs.dll" of Microsoft-Windows-Printing-Reach, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-02-08 16:05:45, Info CSI 00000c08 [SR] Cannot repair member file [l:34{17}]"Amd64\XPSSVCS.DLL" of ntprint.inf, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-02-08 16:05:45, Info CSI 00000c0a [SR] Cannot repair member file [l:22{11}]"xpssvcs.dll" of Microsoft-Windows-Printing-Reach, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-02-08 16:05:45, Info CSI 00000c0b [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2016-02-08 16:05:45, Info CSI 00000c0e [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"xpssvcs.dll"; source file in store is also corrupted
2016-02-08 16:05:46, Info CSI 00000c10 [SR] Cannot repair member file [l:34{17}]"Amd64\XPSSVCS.DLL" of ntprint.inf, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-02-08 16:05:46, Info CSI 00000c11 [SR] This component was referenced by [l:182{91}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.INF_ntprint"







@echo off
rem delete old files
del /q %windir%\logs\cbs\cbs.log
del /q c:\sfcdetails.txt
rem run sfc
sfc /scannow
rem filter out non essential junk from the cbs.log
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >c:\sfcdetails.txt
rem open details in notepad
notepad c:\sfcdetails.txt
rem optional command to shut down & restart pc after running. this may be needed if
rem sfc replaces some critical files. uncomment (remove the 'rem') to activate.
rem shutdown -r
exit
 
I'm not sure how to interpret the errors from the SFCfix script, since they appear to have been written for a specific problem unique to Window 8/8.1. Many of the errors are the "hash mismatch" variety, which would be normal if they are looking for Windows 8/8.1 versions.

On your original sfc /scannow scans in Windows 7, were there only a few corrupt files? Were some repaired and some not? If the Windows 7 installation is working fine, I can't see any reason to risk repairing things that might not need repairing. It is possible, too, if only a few files are involved, to replace them manually using a known-clean source (usually a Windows 7 installation DVD ... or files from a known clean computer of the same version of Windows).
_______________

If you have an extra hard drive available, you have the option to clean install Windows 10 on that, using your Windows 7 product key. That would give you the chance to try it out, and see how well your system runs on 10. [You might find it better to wait a few more months for greater stability / better driver support]. If your computer is store-bought, you could also check on the manufacturer's website & see how the compatibility looks for Windows 10. If this is a custom build, you'd look on the website of the motherboard manufacturer, and probably the video card manufacturer.
_______________

Another tactic: if you've been trying the upgrade through Windows Update, you could try upgrading using a Windows 10 DVD or USB-drive. You can create one using Microsoft's "Media Creation Tool":
Windows 10
(scroll down to the Need to Create USB, DVD, or ISO? section ... you'll find instructions for various options, plus a link to get the Media Creation Tool, a blue option box Download tool now ... )

You can try the upgrade again ... if any internet issues bothered earlier online attempts, the DVD might prove successful. You can also clean install using the DVD, but you'd have to save things beforehand, and reinstall programs and data afterwards. If you only have a dozen or so programs installed, that's not any worse than having to fuss with CBS.logs for weeks.

I generally prefer clean installs (especially of Windows 10), since I'm used to setting up computers quickly [it's what I do everyday, after all]. There are less oddball headaches.
_______________

If you want to try manually replacing the corrupt files, let me know, & I'll see if I can find those instructions again (it's been a while).
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top