Recent Posts

Pages: [1] 2 3 ... 10
I don't think any dated hardware can be resuscitated - it just gets replaced.

Recently I opted to have the motherboard replaced on an old Toshiba Win 7 laptop because the local repair shop was having problems resolving the graphics chip on it.

They eventually managed to source a replacement mobo which turned out to be from the Ukraine and with a slightly earlier AMD graphics than the one it replaced.

In searching for drivers, I came across DriverHub which is a driver updater program which found quite a few drivers for the machine.

I'm not normally keen on those sort of programs but thought this one was impressive.

 Thinking of the many thousands of W7 users attempting to resuscitate dated hardware, though I see little reference to this in your various forums.  Thanks for your time.
I had an experience of chkdsk not picking up on a problem with a HDD but neither did SeaTools for Windows when the trial version of HDSentinel was picking up increasing numbers of bad sectors.

I took its report and changed the HDD.

HDSentinel is a paid for program but you get a 30 day trial and if you uninstall it as I do after using it - that stops the clock on it to use it again as and when.

The first of the Trial versions does for Windows if you want to plug your old HDD back in and see what HDSentinel reports for that.
No, in my case both the upgrade process & clean install failed flagging stated error:

"w 10 upgrade failed
the installation failed in the SAFE_OS phase with an error during REPLICATE_OC operation".

My research tells me this error related to update issue in my case is an ehco of a deeper malaise. I suspect locked data in a bad sector.
 So I used the "gatherstateof.exe" process on my working W7 to generate an XML file, & using the replacement hard drive, completed the fresh install (off line) and  I planted this file in the appropriate location of W 10 :
Copy GenuineTicket.xml to C:\ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket\ and then reboot.

Had I not had this specific error, I "understand" the upgrade process detects / accepts & validates.

Oh - you deserved the Karma for that article :)

An outdated audio driver has been found to cause that error code when updating one Win 10 version to another, so updating drivers before proceeding with any update may help when problems have been found.

An antivirus program can also disrupt an update

So did you revert back to your Win 7 to find that the MCT would install Win 10 and digitally activate using your OEM key ?
The dism /startcomponentcleanup cmd followed by the /restorehealth cmd may have cleared the update problem and helped to produce the clean sfc /scannow result.
Let me tell you the back story of my migration W7 to W 10 adventure:
W 7 was showing error : 8007001f - 0x2006, this displayed being unable to install an update.
Ran the online MS update tool, SFC /scannow, Chkdsk C: /f, none of which detected an issue.
Disabled the relevant services & renamed Software distribution folder yet the error persisted.
Remember I had full functionality apart from this.
I attempted to upgrade my system to W 10 through the M S media creation tool and late into the process the same error. (8007001f - 0x2006) At this point I replaced the hard drive
A clean install requested a Win key, unlike the upgrade process, and here my retrieved OEM  key was rejected.  And days of research produced my solution which I posted.
Boggin,you & Shane  over the years  have helped me sort various software issues that were way above my pay grade!
So being awarded a Karma point from you is an unexpected pleasure!
Thanks, now it says it didn't find any violations.
General & Misc. / MOVED: repairing windows update corrupted system
« Last post by Boggin on January 19, 2020, 01:39:37 AM »
This topic has been moved to Programs & Site Help & Support
I create a system image before test running the repair program so I can restore should things go awry.

These cmds run from a Command Prompt (Admin) can resolve most Win 10 problems - (I assume you are using Win 10 ?)

dism /online /cleanup-image /startcomponentcleanup

(That one cleans up the WinSxS folder of obsolete updates which can cause update problems, but because it can remove GBs of data, it may be worth checking to see if the HDD would benefit from a defrag if applicable).

dism /online /cleanup-image /restorehealth

sfc /scannow

shutdown /r /t /00

That one effects an immediate reboot but there are also the following cmds which will reset the update components and which you can copy & paste en bloc to the cmd prompt where they'll auto run, except perhaps for the last one where you may need to press enter.

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 catroot2.old

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

The SoftwareDistribution.old cmd removes your update history but does not affect installed updates, but if you've already run the Update repair in the program, then that history has already been removed.

Windows also has its own update troubleshooter.
Pages: [1] 2 3 ... 10