M
munro henry
My PC was offered the opportunity to install the May 2020 W10 feature upgrade. However, the upgrade failed, with error 0x80029c4a . An earlier upgrade had also failed, essentially because of a faulty hard drive and some files missing in one area. I was then able to examine a log file, see where the error occurred and copy across the missing files from the laptop.
Greg Carmack - MVP 2010-2021 advised holding off as the new version still had problems and waiting for things to be sorted. The thread is now locked, so I can't respond directly. Autumn came, v 20H2 arrived and still no success updating. I knew I had to update some time as earlier version of W10 were being taken off support - some time in the next few years my v1909 would become unsupported.
I'd worked out how to read .etl files using PowerShell with the Get-WindowsUpdateLog command, but to little avail in this case.
The game changer was a thread that suggested using the System File Checker (SFC) utility on www.800error.com . "This handy in-built tool will check your file system.
1. Click Start and type "cmd".
2. In your search results cmd should show up with an black icon.
3. Right-click it and select Run as administrator.
4. If you are prompted for the admin password, enter the password and click OK.
5. A new completely black window will open. You can type commands directly into this window.
6. Type sfc/scannow and press Enter.
7. This process will take a long time. You can minimize this black windows and work on.
Come back to the black window after a time and check if the process finished.
As soon as the SFC process finished, restart your computer. After the restart you search for Updates again."
SFC came up with a lot of fragmented files, presumably arising from the old hard disc and the files persisting. The message was that the files had all been repaired.
When I tried to update, progress sailed past where it had stopped before with error 0x80029c4a. However it did fail with error 0x80070005, a permissions error. But, when I did the last step and restarted the PC I was gratified that it sailed through the update.
If only I'd been aware of SFC when I was trying to get going again after replacing my faulty hard drive - could have saved time then too!
Chapeau to Greg (for letting me hold off for the instant) and www.800error.com (for providing the solution) on post Solution to Windows Update error 0x80029c4a - solved with fix!
Continue reading...
Greg Carmack - MVP 2010-2021 advised holding off as the new version still had problems and waiting for things to be sorted. The thread is now locked, so I can't respond directly. Autumn came, v 20H2 arrived and still no success updating. I knew I had to update some time as earlier version of W10 were being taken off support - some time in the next few years my v1909 would become unsupported.
I'd worked out how to read .etl files using PowerShell with the Get-WindowsUpdateLog command, but to little avail in this case.
The game changer was a thread that suggested using the System File Checker (SFC) utility on www.800error.com . "This handy in-built tool will check your file system.
1. Click Start and type "cmd".
2. In your search results cmd should show up with an black icon.
3. Right-click it and select Run as administrator.
4. If you are prompted for the admin password, enter the password and click OK.
5. A new completely black window will open. You can type commands directly into this window.
6. Type sfc/scannow and press Enter.
7. This process will take a long time. You can minimize this black windows and work on.
Come back to the black window after a time and check if the process finished.
As soon as the SFC process finished, restart your computer. After the restart you search for Updates again."
SFC came up with a lot of fragmented files, presumably arising from the old hard disc and the files persisting. The message was that the files had all been repaired.
When I tried to update, progress sailed past where it had stopped before with error 0x80029c4a. However it did fail with error 0x80070005, a permissions error. But, when I did the last step and restarted the PC I was gratified that it sailed through the update.
If only I'd been aware of SFC when I was trying to get going again after replacing my faulty hard drive - could have saved time then too!
Chapeau to Greg (for letting me hold off for the instant) and www.800error.com (for providing the solution) on post Solution to Windows Update error 0x80029c4a - solved with fix!
Continue reading...