Solved Cannot install IE10 on Win 7 x64 on Dell Latitude

[jruiz22]

Hello, I need help repairing my Windows in order to upgrade to IE 10.

I am getting error code 9C59.

I ran the SURT - Windows6.1-KB947821-v26-x64.msu

Attached is my CheckSUR.log, please let me know what I need to do to correct this problem.

I ran SFC /SCANNOW and have attached sfcdetails.txt file as well.

Thanks

 

[NoelDP]

You have some fairly major system corruption....
From the CheckSUR

Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-ie-controls.resources_31bf3856ad364e35_9.4.8112.16443_en-us_2273b6e38a9560e7.manifest
 winsxs\manifests\amd64_microsoft-windows-i..rolviewer.resources_31bf3856ad364e35_9.4.8112.16443_en-us_16feb7e28f502777.manifest
 winsxs\manifests\amd64_microsoft-windows-ieframe.resources_31bf3856ad364e35_9.4.8112.16443_en-us_0450e72ea0608423.manifest
 winsxs\manifests\amd64_microsoft-windows-i..onmanager.resources_31bf3856ad364e35_9.4.8112.16443_en-us_0979a9e1a2043663.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-setup.resources_31bf3856ad364e35_9.4.8112.16443_en-us_c5b84a42a315520e.manifest
 winsxs\manifests\amd64_microsoft-windows-i..kitengine.resources_31bf3856ad364e35_9.4.8112.16443_en-us_58a237eda551fefe.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-feedsbs.resources_31bf3856ad364e35_9.4.8112.16443_en-us_bd048d99aae88a13.manifest
 winsxs\manifests\amd64_microsoft-windows-i..trolpanel.resources_31bf3856ad364e35_9.4.8112.16443_en-us_97154455bade5049.manifest
 winsxs\manifests\amd64_microsoft-windows-i..filercore.resources_31bf3856ad364e35_9.4.8112.16443_en-us_d812f0b2c6de824a.manifest
 winsxs\manifests\amd64_microsoft-windows-i..rendering.resources_31bf3856ad364e35_9.4.8112.16443_en-us_81730a84d61f5330.manifest
 winsxs\manifests\amd64_microsoft-windows-i..rofilerui.resources_31bf3856ad364e35_9.4.8112.16443_en-us_be56672dd6eea4bf.manifest
 winsxs\manifests\amd64_microsoft-windows-i..tbranding.resources_31bf3856ad364e35_9.4.8112.16443_en-us_6ac95865d9f23ccb.manifest
 winsxs\manifests\amd64_microsoft-windows-i..explorer-deployment_31bf3856ad364e35_9.4.8112.16443_none_c251ee64ebbd3509.manifest
 winsxs\manifests\x86_microsoft-windows-i..ntrolpanel-optional_31bf3856ad364e35_9.4.8112.16443_none_862586c1332c1d0b.manifest
 winsxs\manifests\amd64_microsoft-windows-i..orer-oob-deployment_31bf3856ad364e35_9.4.8112.16443_none_c8eb3eb49f72f8f6.manifest
 winsxs\manifests\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.30729.6161_none_51cd0a7abbe4e19b.manifest
 winsxs\manifests\msil_system.design_b03f5f7f11d50a3a_6.1.7601.17966_none_89ab3041bfbe7442.manifest
 winsxs\manifests\msil_system.directoryservices.protocols_b03f5f7f11d50a3a_6.1.7601.17966_none_837b7fa210fd83d6.manifest
 winsxs\manifests\amd64_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_7.6.7600.256_none_9286cad7bab620de.manifest
 winsxs\manifests\x86_microsoft-windows-virtualpc-additions_31bf3856ad364e35_7.1.7600.16393_none_fa50c45d13592d39.manifest
 winsxs\manifests\msil_system.directoryservices.protocols_b03f5f7f11d50a3a_6.1.7601.22126_none_6ca9dae42aa878ce.manifest
 winsxs\manifests\amd64_72eca7b5ceeb2568f653dc818af98453_b03f5f7f11d50a3a_6.1.7601.17587_none_22dd77a2b8e92492.manifest
 winsxs\manifests\amd64_81078092d4d98b95dc52fb6ce54495bb_b03f5f7f11d50a3a_6.1.7601.21693_none_223376243cd12b7e.manifest
 winsxs\manifests\x86_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7601.17587_none_ff8490d1c3813994.manifest
 winsxs\manifests\amd64_win7-microsoft-wind..oyment-languagepack_31bf3856ad364e35_7.1.7601.16492_ko-kr_5a15022f252c077f.manifest
 winsxs\manifests\amd64_microsoft-windows-n..-deployment-netfx20_31bf3856ad364e35_6.2.7600.16513_none_9adfccf5ffc9e41e.manifest
 winsxs\manifests\msil_system.design_b03f5f7f11d50a3a_6.1.7601.22126_none_72d98b83d969693a.manifest
 winsxs\manifests\msil_system.directoryservices.resources_b03f5f7f11d50a3a_6.1.7601.17966_en-us_0dbb286c9035e5e2.manifest
 winsxs\manifests\msil_system.directoryservices.resources_b03f5f7f11d50a3a_6.1.7601.22126_en-us_f6e983aea9e0dada.manifest
 winsxs\manifests\x86_microsoft-windows-ie-htmlactivexcompat_31bf3856ad364e35_9.4.8112.16443_none_2fdb70c12a1e1e73.manifest
 winsxs\manifests\x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16443_none_a89ae7d964e5586a.manifest
 winsxs\manifests\x86_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_9.4.8112.16443_none_a7a5a98a6c2d4c7c.manifest
 winsxs\manifests\x86_microsoft-windows-ie-ieproxy-legacy_31bf3856ad364e35_9.4.8112.16443_none_c4b8662176f5e118.manifest
 winsxs\manifests\x86_microsoft-windows-ie-setup-support_31bf3856ad364e35_9.4.8112.16443_none_de3cb89e78ce0573.manifest
 winsxs\manifests\wow64_microsoft-windows-ie-directxtransforms_31bf3856ad364e35_9.4.8112.16443_none_16a5985f88b7019d.manifest
 winsxs\manifests\wow64_microsoft-windows-ie-datacontrol_31bf3856ad364e35_9.4.8112.16443_none_92e6723aa73c93da.manifest
 winsxs\manifests\wow64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.8112.16443_none_e381b5efb531f87f.manifest
 winsxs\manifests\x86_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16443_none_551baf7cf0eec21f.manifest
 winsxs\manifests\wow64_microsoft-windows-ie-behaviors_31bf3856ad364e35_9.4.8112.16443_none_bba2cdfef920c97e.manifest
 winsxs\manifests\x86_microsoft-windows-ie-lowreg_31bf3856ad364e35_9.4.8112.16443_none_c0b8357bfe359ea8.manifest
 winsxs\manifests\wow64_microsoft-windows-scripting-jscript_31bf3856ad364e35_9.4.8112.16443_none_01bf31e6fe374643.manifest
 winsxs\manifests\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16443_none_1a54f6f7bc27cdeb.manifest
 winsxs\manifests\x86_microsoft-windows-ie-ratings_31bf3856ad364e35_9.4.8112.16443_none_dffe41ce770ff6cc.manifest
 winsxs\manifests\x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_9.4.8112.16443_none_cd4f1b55f11ea758.manifest
 servicing\packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.mum
 servicing\packages\Microsoft-Windows-UIAnimation-WinIP-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.mum
 servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.cat
 servicing\packages\Microsoft-Windows-UIAnimation-WinIP-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.cat
 servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat

From the SFC scan

2013-04-03 01:53:50, Info                  CSI    0000044d [SR] Repairing 42 (0x000000000000002a) components

all of which failed - because of the lack of the proper manifest and package files.

I'll post a fix protocol later, but it could take a while

 

[NoelDP]

I'm having trouble sourcing an update for IE9 that is giving many of the errors found. It may be an update that's been withdrawn, or I may just be missing it in my search.

We'll go with what I've found so far....


I've uploaded a file - j22aa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder j22aa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[jruiz22]

Thank you very much for your NoelDP, I have finished the CheckSUR tool again after copying your files.

It appears the file got a little bit longer, but some of the stuff you sent no longer appears on the list.

 

[NoelDP]

Great - the file has done what it was supposed to do, and cleared the decks a bit

Now I'll have to concentrate on the 18 Watchlist errors and see where they get us.

back a bit later.
... just for reference....

Checking Package Watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-NetFx2-ServerCore-OC-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-NetFx2-ServerCore-OC-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Printing-ServerCore-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-UIAnimation-WinIP-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-UIAnimation-WinIP-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492 Package registry presence failed, possibly an orphaned package on package watchlist
Checking Component Watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_2b9bb45b11d2fcbc Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_2b9bb45b11d2fcbc Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_2b9bb45b11d2fcbc Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_2b9bb45b11d2fcbc Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 msil_system.windows.forms_b77a5c561934e089_6.1.0.0_none_0a57c6e724b6dfa9 Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 msil_system.windows.forms_b77a5c561934e089_6.1.0.0_none_0a57c6e724b6dfa9 Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_cf7d18d759758b86 Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_cf7d18d759758b86 Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_cf7d18d759758b86 Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_cf7d18d759758b86 Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist

 

[NoelDP]

We'll deal with the Component list first.

Please open an Elevated Command Prompt, and run the following commands

REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_2b9bb45b11d2fcbc" >>%userprofile%\desktop\npwcom.log
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_cf7d18d759758b86" >>%userprofile%\desktop\npwcom.log
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\msil_system.windows.forms_b77a5c561934e089_6.1.0.0_none_0a57c6e724b6dfa9" >>%userprofile%\desktop\npwcom.log
 
.

That should create a file on your desktop 'npwcom.log'
Please attach it to your reply.

 

[jruiz22]

Attached is the 'npwcom.log'

 

[NoelDP]

Argh - a typo on my part

Please try again with the *corrected* commands above!

 

[jruiz22]

Hey no problem, here is the new file

 

[NoelDP]

That's more like it!
The results are as expected
Now comes the difficult and dangerous bit.

How confident are you in Regedit?
We have to manually adjust permissions before we make changes - and then adjust them back afterwards.
I'm OK doing this fix for myself - but I've never tried talking anyone through it on the forums.

There are two ways
1) If you're reasonably confident, you can do the whole thing manually, and individually (possibly the best way)
2) If you're not confident, then we can limit your involvement to one permissions change before running a registry file. and one permissions change after.

Your choice.
:devil:

 

[jruiz22]

I like to live on the wild side, let's do this the best way. But please, no typos on this step?

 

[NoelDP]

It's OK - I'll test this one first!

It's going to take me a while to work up the command file - back later.

In the meantime, please ensure that you create a System Restore point (preferably two!)

 

[jruiz22]

I like to live on the wild side, let's do option 1. But please no typos this time if it is that dangerous.

 

[NoelDP]

WARNING - These instructions apply ONLY to this poster, in this thread. Following them on your own machine WILL break things!

Here's the detailed instructions for the first Key modifications to make - if all goes well, I'll post the other two later

Open Regedit
Navigate to the
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect
key
and find the
amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_2b9bb45b11d2fcbc
subkey
right-click on the subkey to highlight it and select Permissions

Click on the Advanced button
Click on the Owner tab
highlight 'Administrators' in the box, and click Apply
put a tick in the 'Replace owner...' box, and click Apply
Click on the Permissions tab
highlight Administrators
Click Edit
put a tick in the Allow/Full Control box and click OK
put a tick in the 'Replace all child...' box and click Apply
Accept the warning
Click OK twice to get back into Regedit

in the right pane, look for the following values
Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1
Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.2522422-4_neutral_LDR
Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.2522422-5_neutral_LDR
Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.2522422-6_neutral_GDR

Delete each - highlight it and hit the delete button - accept the warning if you're sure you got the right one
THERE IS NO UNDO OPTION IN REGEDIT!


Now we have to get permissions back to where they should be....
right-click on the subkey name again, and select Permissions
Click on Advanced
There should be two entries for Administrators
Highlight Administrators (with Full Control - not inherited) - make sure that the other Administrators entry with Read permissions still exists!
click Remove
Click on the Owner tab
Click 'Other users or groups'
in the box, type
NT SERVICE\TrustedInstaller
and click on 'Check Names' - the entry should change to TrustedInstaller
click OK three times
...and you should be back in Regedit
Close Regedit, and reboot

Now run CheckSUR again, and we'll see how you did

Then we'll deal with the other two keys...

WARNING - These instructions apply ONLY to this poster, in this thread. Following them on your own machine WILL break things!

 

[NoelDP]

... all that just to delete three entries in a database!

I need a drink!

 

[jruiz22]

LOL, If you want just send me the next three lines, i will reuse the permission instructions from the previous post.

I owe you at least a few few drinks.

Here is the latest logs, seems to be getting smaller now

 

[NoelDP]

Great - that looks fine so far.

Here's the subkey and value listing....
Still under the same Key....
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect

x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_cf7d18d759758b86
Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.2522422-1_neutral_LDR
Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.2522422-2_neutral_LDR
Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.2522422-3_neutral_GDR
Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1

msil_system.windows.forms_b77a5c561934e089_6.1.0.0_none_0a57c6e724b6dfa9
Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0.2518869-18_neutral_LDR
Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0.2518869-19_neutral_GDR

run another CheckSUR after that, and we'll work on the Watchlist Packages next - same procedure

 

[jruiz22]

I am going to have to figure out in these logs how you know what to delete. This is fun. Thanks

 

[NoelDP]

Well done - that's eliminated the Components errors.
Before I start you off on the Package errors, we'd better have a backup....
Open an Elevated Command Prompt, and run the following commands

REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0" >>%userprofile%\desktop\npwpack.log
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-NetFx2-ServerCore-OC-Package~31bf3856ad364e35~amd64~~0.0.0.0" >>%userprofile%\desktop\npwpack.log
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-NetFx2-ServerCore-OC-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0" >>%userprofile%\desktop\npwpack.log
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~~0.0.0.0" >>%userprofile%\desktop\npwpack.log
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Printing-ServerCore-Package~31bf3856ad364e35~amd64~~0.0.0.0" >>%userprofile%\desktop\npwpack.log
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-UIAnimation-WinIP-Package~31bf3856ad364e35~amd64~~0.0.0.0" >>%userprofile%\desktop\npwpack.log
 
.

That will create a new npwpack.log file - which may be big enough to make it worth zipping before uploading (it's 68KB on my test machine)
Upload it and I'll check things before I post the 'fix list'.

 

[NoelDP]

p.s. You've got a very strange idea of fun!