Windows 8 Pro

[boco]

Looks like it is b0rked.

Open a command line with Administration rights and try the following repair commands:

Code: Select all

sfc /scannow

Code: Select all

Dism /Online /Cleanup-Image /RestoreHealth

[mhaxx]

Done:

- stop WU service
- del C:\Windows\SoftwareDistribution
- start WU service
- sfc /scannow
- Dism /Online /Cleanup-Image /RestoreHealth
- again sfc /scannow
- again Dism /Online /Cleanup-Image /RestoreHealth
- restart

If now I launch the updates search from the official WU I get the same error: 8007000E

FYI:
- sfc gives message like: ... found and fixed damanged file ... details in windir\Logs\CBS\CBS.log
- Dism gives message like: ... restore operation failed ... the origin of the restore wasn't found or the archive of the components not restorable ...error 0x800f081f ... impossible to run.. distr. image... no operation was performed.. ... details in C:\Windows\Logs\DISM\dism.log

[boco]

0x8007000E = Out of memory (RAM). Usually occurs with the long search problem.

Regarding 0x800f081f - Did you run cleanmgr with Windows Update Cleanup? Looks like that error happens because cleanmgr removes too many update backups.



I guess a reinstallation with a clean Win 8.1 source is inevitable...

[mhaxx]

What's cleanmgr with Windows Update Cleanup? how to?

[boco]

cleanmgr is the disk cleanup tool, to remove temporary files. I just remembered that Windows 8 and higher do run it automatically as part of their maintenance task. Windows Update Cleanup removes old Update information and files from the Side-By-Side (SxS) repository, and it applies special compression for lighten Windows footprint. Unfortunately, it sometimes removes too much, causing those 0,800f081f errors...

You might have to bite the bullet and clean install Win 8.1, to get back to a clean slate.

I cannot offer further help with a corrupt Windows installation, and MS will not offer help (as Windows 8.0 is unsupported).

[mhaxx]

I run disk cleanup tool (it removed about 700 Mb) however the problem remained..

Let me ask a question: disk cleanup tool works on WU repo, but if you use WSUSOU that repo isn't used so WSUSOU should work, right? Again: if WU has mem problems, WSUSOU couldn't have because it's minimal, etc.. right?

And let me underline a fact: when I apply the updates through WSUSOU (with success) the installation process fails during Windows startup, so I don't think the problem is WU but maybe some of those updates find problems.. Can't we investigate from WSUS log which problems are?

Thanks your support in any case.

[aker]

You can investigate the problem this way:
- Use wsusou to update your system, but: cancel the process (by closing the cmd-window) after 5-10 updates
- Wait about 2 minutes
- Reboot the computer
- check, if it worked
If yes: continue
If no: check update by update; as soon as you got the broken one, exclude it using .\client\exclude\custom\ExcludeList.txt

[mhaxx]

FYI this is WU log: http://tinyurl.com/zudm7yg

I've just relaunch WSUSOU update process:

Listing update files...
Warning: Update kb3105216 (id: 3d64df70-8eeb-4bc5-83b6-20589d787f30) not found.
Warning: Update kb3114872 (id: 37d5642c-8e2e-42cf-aabf-a1e77714281b) not found.
Warning: Update kb3162593 (id: 3dbae6fb-1a34-45d1-b199-dd05ebfe833b) not found.
Warning: Update kb3114400 (id: 98015a12-b9cd-48ab-bd7f-7dea92bb8f67) not found.
Warning: Update kb3114340 (id: 78e4ae09-a5c7-43ed-858d-e24253bbe68b) not found.
Warning: Update kb3115431 (id: e6c1f59c-6ce8-4dee-bf36-bf059f888e79) not found.
Info: Skipping update kb890830 (Malicious Software Removal Tool) due to matching black list entry.

What do these warning mean? can I ignore?

Anyway the next step is:

Installing updates...
Installing update 1 of 4...
Verifying integrity of ..\w62\glb\windows8-rt-kb3078601-x86_b8af5a5d069404083dae
df8c533cd61299e3bb56.cab...
hashdeep.exe: Audit passed
Installing ..\w62\glb\windows8-rt-kb3078601-x86_b8af5a5d069404083daedf8c533cd612
99e3bb56.cab...
Installing update 2 of 4...
Verifying integrity of ..\w62\glb\windows8-rt-kb3087039-x86_574de5f07bfdc1861fe5
0176f5f40d8b208b3cd9.cab...
hashdeep.exe: Audit passed
Installing ..\w62\glb\windows8-rt-kb3087039-x86_574de5f07bfdc1861fe50176f5f40d8b
208b3cd9.cab...
Installing update 3 of 4...
Verifying integrity of ..\w62\glb\windows8-rt-kb3109094-x86_2f3e1bd49b219042b98c
af1c98af92a04ac92812.cab...
hashdeep.exe: Audit passed
Installing ..\w62\glb\windows8-rt-kb3109094-x86_2f3e1bd49b219042b98caf1c98af92a0
4ac92812.cab...
Installing update 4 of 4...
Verifying integrity of ..\w62\glb\Windows8-RT-KB2937636-x86.msu...
hashdeep.exe: Audit passed
Installing ..\w62\glb\Windows8-RT-KB2937636-x86.msu...
Warning: Installation of ..\w62\glb\Windows8-RT-KB2937636-x86.msu failed (errorl
evel: -2145124329).
Installation successful. Please reboot your system now.

Now if I reboot, the installation finalization fails during restart.

[mhaxx]

P.S. how can I exclude a certain update? (wsusoffline1032\exclude\custom)

[mhaxx]

Installing updates...
Installing update 1 of 4...
Verifying integrity of ..\w62\glb\windows8-rt-kb3078601-x86_b8af5a5d069404083dae
df8c533cd61299e3bb56.cab...
hashdeep.exe: Audit passed
Installing ..\w62\glb\windows8-rt-kb3078601-x86_b8af5a5d069404083daedf8c533cd612
99e3bb56.cab...
Installing update 2 of 4...
Verifying integrity of ..\w62\glb\windows8-rt-kb3087039-x86_574de5f07bfdc1861fe5
0176f5f40d8b208b3cd9.cab...
hashdeep.exe: Audit passed
Installing ..\w62\glb\windows8-rt-kb3087039-x86_574de5f07bfdc1861fe50176f5f40d8b
208b3cd9.cab...

==> I stopped the process at this point, so that only the first update was installed (kb3078601), however also this time the Windows restart failed the installation!

Have I to think this is the update to exclude? Mmm...