How To Fix ERROR. And whenever something takes me ages, rather than write it down in my personal notes, I prefer to put it out online for everyone with the same problem to easily find and benefit from. The problem I'm talking about today is trying to upgrade your Windows 7 installation to SP1 by applying Microsoft's update KB9. The same problem may affect 3.
![]() Thanks, Artem! Thought I was faced with a complete reinstall as my laptop not provided with Windows disks – only recovery disks to revert to factory condition. We hebben gemerkt dat er heel wat gebruikers recent problemen ondervinden met DVD’s met onze kaarten. Dit heeft te maken met het Windows-systeembestand secdrv.sys. I'm not sure what the update number for that would be, but the solution should work for either one. The update starts just fine, chugs along for 1. You end up with this message (code 8. I can't take credit for it – all I did was spend a month weeding through the crap, retrying, and getting nowhere, until a genius by the name Ben- IS came up with exactly the right diagnosis and provided exactly the right solution. This solution, in my own interpretation, is below. Step 1. We are going to use a utility called SFC (System File Checker or Windows Resource Checker), which is part of the Windows installation. It will help diagnose the problem. Open up a command prompt (cmd) as administrator and runsfc /scannow. This will run for a while and produce a file called CBS. WINDIR%\Logs\CBS (usually C: \Windows\Logs\CBS). See this KB9. 29. ![]() SFC and CBS (Component Based Servicing). Beginning system scan. Verification 1. 00% complete. Windows Resource Protection did not find any integrity violations. Even though there are no integrity violations, we should have enough info in the log to diagnose the problem. Step 2. Unfortunately, Windows overwrote my CBS. I'll go by the one Ben- IS provided. Open up CBS. log and look for something like Failed uninstalling driver updates or 0x. ERROR. In my case, it was: sto: Failed to find driver update 'C: \Windows\Win. Sx. S\amd. 64. Error = 0x. Step 4. This is the key to the whole operation. Open up the command prompt again (cmd) as administrator and runpnputil - a INSERT. Published name : oem. Total attempted: 1 Number successfully imported: 1. Repeat this step for any failures found in step 3. Step 5. Apply the SP1 Windows Update again – it should now install successfully. And voila – enjoy your SP1! Microsoft has failed to fix this incredibly cryptic problem, leaving it up to the users to figure out why their SP1 updates are not installing. Thanks to people like Ben- IS, solutions no longer involve head- banging, postal rage, and f. Follow Artem on Twitter (@Artem. R) or subscribe to the RSS feed. In the meantime, if you found this article useful, feel free to buy me a cup of coffee below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |