Need some files for CheckSUR fix

RyanW · 10 May 2015

Code:

Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-05-11 02:33
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Payload File Missing 0x00000000 packager.dll x86_microsoft-windows-packager_31bf3856ad364e35_6.1.7601.17727_none_f00fad2d2f059967 
(f) CSI Payload File Missing 0x00000000 packager.dll amd64_microsoft-windows-packager_31bf3856ad364e35_6.1.7601.17727_none_4c2e48b0e7630a9d 
Summary:
Seconds executed: 876
 Found 2 errors
  CSI Payload File Missing Total count: 2

Only the Payload File Missing errors left now. Logs etc. here.

NoelDP · 11 May 2015

Great!
I'll post the patch later.

NoelDP · 11 May 2015

I've uploaded a file - rywak.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\rywak
hit the enter key - if you get a 'Not Found' error try
DIR D:\rywak
or
DIR E:\rywak

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\rywak <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

RyanW · 11 May 2015

sfc found no integrity violations (but then it again it never did during this entire saga). I ran CheckSUR after that and here's the log:

Code:

Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-05-11 12:40
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 728
 No errors detected

More logs here. So, is that finally a clean bill of health? :)

NoelDP · 11 May 2015

All looks good to me!

Does Windows Update work?

RyanW · 11 May 2015

NoelDP said:

Does Windows Update work?

Not sure. All I'm seeing is an optional KB3022345 but don't know whether I should install it. Any idea?

NoelDP · 11 May 2015

I'dhold off on that one. its known to be buggy!
nothing else?

Layback Bear · 11 May 2015

I just hid KB3022345 without any bad things happening.

RyanW · 11 May 2015

NoelDP said:

I'dhold off on that one. its known to be buggy!

Apparently this is a fixed version, but you're right, why be hasty? I'll probably have to wait for something useful before I can confirm that Windows Update works with no errors.

NoelDP said:

nothing else?

No, as I mentioned in my 3rd post:

RyanW said:

Note that Windows Update (after a long time) now finally says that the system is up to date, but I want a clean bill of health from CheckSUR.

This is the first update I've been offered since then.

Layback Bear said:

I just hid KB3022345 without any bad things happening.

Hiding a buggy optional update shouldn't cause any issues ever, only installing it should. :)

NoelDP · 11 May 2015

The update is only to flag Windows 10 as being available, and assist in the upgrade anyhow - so it an be safely ignored. If/when it gets updated again, then it will reappear in your download list.