[SOLVED] Windows 7-64 KB4487078 Won't install

[aalflyguy]

Windows 7-64 KB4487078 Won't install.
I've taken a variety of Microsoft fixes. No Help.
Scannow Completed with no issues. No Help.
Windows Update Troubleshooter Completed with 2 fixes. No Help.
SFCFix Completed Completed with no issues. No Help.

 

[aalflyguy]

Microsoft issued an update today for KB4487078. This new update, KB4487256, issued exactly one week later, has exactly the same wording as the first, other than the KB number:

2019-02 Preview of Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 7 and Server 2008 R2 for x64 (KB4487256)

I attempted to download and install this new Windows Update with no success and received the same Error Code 2 that I received with KB4487078. That Error Code is a dead end with no resolution. I have been in contact with Microsoft Technical Support. They have not been able to resolve the issue either. They advised me to continue installing Windows Updates which hopefully will eventually resolve this issue. Stay tuned.

 

[Sysnative Windows Update]

Hello and welcome!

Let me know if further assistance is required.

 

[aalflyguy]

Any MVP staff member who has a clue on how to fix this, please respond.
Update: Level 2 Microsoft Technical Support concluded today with no solution. He attempted to fix the problem by downloading and installing a Hotfix:
System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) That was unsuccessful, so, after sending a wealth of info from my PC, he escalated the problem to Level 3 who will contact me on or before 02/24/2019. If ur interested, stay tuned.

 

[Sysnative Windows Update]

I can attempt to fix it if you wish.

 

[Sysnative Windows Update]

Please keep all your questions in this thread. We do not provide PM assistance.

Let's start by you downloading the following update: Microsoft Update Catalog

Within it you will see multiple files available for download. Please attempt to download and run them all one by one.

When done, please report the result.

As an experienced Windows Update Analyst, I sincerely recommend that you do not install any update that has Preview of... in its name due to the dangers (this is essentially beta software and can cause issues in the long run).

Thank you.

Can you elaborate further on KB947821 being unsuccessful? Did the tool complete and report successful installation? If so, there was a file called CheckSUR.log created in C:\Windows\Logs directory

Please copy it to your Desktop and then attach it here for my review.

With some luck, we should be able to resolve this sooner than MS does.

 

[aalflyguy]

I'll run the items in the Microsoft Update Catalog and let u know the results later. And yes KB947821 installed successfully. The CheckSUR text file is attached. Thanks for the help.

 

[Sysnative Windows Update]

Good. SURT appears to have fixed everything it found.

Proceed with the Catalog as instructed.

 

[aalflyguy]

I had forgotten when this all started that I had downloaded and run all of the items in the Microsoft Update Catalog (MUC), except one from the new KB4487256 Windows Update, issued yesterday, 02/19/2019. The response from that new item was similar to the responses that I received running the MUC items for KB4487078, the original Windows Update issued 02/12/2019, that started this mess. Some of the items from that latter MUC run were installed, but most responses were similar to this new response: "Does Not Apply or Blocked by Another Condition on Your Computer." I'm not sure what else I should download or check for in the MUC.

 

[Sysnative Windows Update]

Okay, when you check for updates. Which are listed as needed (only Important)?

 

[aalflyguy]

I have no idea what that means. Are u talking about the MUC or Windows Update? I'm up to date on all Windows Updates except for the original problem Update KB4487078, then followed a week later by the identical Update KB4487256.

 

[Sysnative Windows Update]

What I meant was, when you enter Windows Update into Search and open it, which updates are shown:



KB4487256 should not be installed as it is a preview. So the goal here (if I understood you correctly) is to install KB448707.

Please try installing it again and when it fails, attach CBS.log and do the following:

Using the .NET Collect Utility

1. Download collect.exe and save to your desktop.
2. Go ahead and run the tool
3. The utility creates a compressed cabinet of all the needed logs to %TEMP%\vslogs.cab.
4. Please zip/attach to this post or if too large, send using a service such as SendSpace.

 

[aalflyguy]

Attached are the results after attempting to download and install Windows Update (WU) KB4487078. I understand your concern for the Preview WU KB4487256, even though, except for the word "Preview", is identical to KB4487078. WU KB4487256 was issued exactly one week after KB4487078, likely as a preview to find if it would "fix" the issues customers were having with KB4487078. The failed WUnpic has 2 pages. The second page is the page that comes up after clicking on "Get help with this error", pretty much a dead end or no help. The last attached file is what I think you want, but not sure. There was no %TEMP%\vslogs.cab The closest file was called %TEMP%\vslogs.zip. I copied everything within this: C:\Users\PAULLU~1\AppData\Local\Temp\vslogs\Temp. All of those files are included individually since I wasn't certain what you wanted. Obviously, you'll let me know if I dropped the ball.

 

[Sysnative Windows Update]

Thank you. Your CBS.log has uncovered the following error:

19-02-21 04:29:34, Error                 CSI    0000000f (F) STATUS_MEDIA_WRITE_PROTECTED #3257951# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysSetInformationFile(flags = (AllowNotSameDevice), h = 16c6c ("\Device\HarddiskVolumeShadowCopy58\Windows\winsxs\ManifestCache\548c1bd2e27235ea_blobs.bin"), iosb = @0x122d370, buff = @0x361a70, bufflen = 244 (0x000000f4), ic = 10 (0x0000000a), disp = Invalid)
[gle=0xd00000a2]
2019-02-21 04:29:34, Error                 CSI    00000010@2019/2/21:10:29:34.494 (F) d:\w7rtm\base\wcp\sil\merged\ntu\ntsystem.cpp(2530): Error STATUS_MEDIA_WRITE_PROTECTED originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysSetInformationFile expression: (null)
[gle=0x80004005]
2019-02-21 04:29:34, Error                 CSI    00000011 (F) STATUS_MEDIA_WRITE_PROTECTED #3257949# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::TransferFile(flags = (ReplaceIfExists|OpenForBackupIntent|MissingFileIsOk), op = [4]"Move", odir = NULL, oname = [l:208{104}]"\??\GLOBALROOT\Device\HarddiskVolumeShadowCopy58\Windows\WinSxS\ManifestCache\548c1bd2e27235ea_blobs.bin", ndir = NULL, nname = [l:220{110}]"\??\GLOBALROOT\Device\HarddiskVolumeShadowCopy58\Windows\WinSxS\ManifestCache\08eca656d0c9d40103000000fc13c04c", disp = (null))
[gle=0xd00000a2]
2019-02-21 04:29:34, Error                 CSI    00000012 (F) STATUS_MEDIA_WRITE_PROTECTED #3257940# from ComponentStore::CRawStoreLayout::RenameAwayManifestCacheBlobfileAttempting to RenameAwayManifestCacheBlobfile. Current blobfile name: [l:52{26}]"548c1bd2e27235ea_blobs.bin"
[gle=0xd00000a2]
2019-02-21 04:29:34, Error                 CBS    Failed to get offline CSI store. [HRESULT = 0x80070013 - ERROR_WRITE_PROTECT]
2019-02-21 04:29:34, Error                 CBS    Failed to initialize store parameters with boot drive: T: and windows directory: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy58\Windows\ [HRESULT = 0x80070013 - ERROR_WRITE_PROTECT]

Take this steps to remedy it:

1. Open Control Panel > System and Security > System and click on System protection.


2. Under Protection Settings, click to select the System Disk and then click Configure.


3. Here click on ‘Delete all restore points (this includes system settings and previous versions of files).


4. Click Apply/OK.


And retry installing KB4487078.

Should it fail, provide the same logs as above.

 

[aalflyguy]

Same reply...Failed Update with the same screen previously sent. New CBS attached.

 

[Sysnative Windows Update]

Let's dig deeper:


Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the update just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log

It will likely be too big, so you should use a file sharing service of your choice.

 

[aalflyguy]

OK, that took awhile...Hours. Process Monitor stopped recording/failed at 86%. During the Save To File process, stopped at about 84%. CBS file is attached. The LogFile.zip is too large even after transferring it to OneDrive. When I attempted to attach it here from OneDrive, Sysnative says it's too large for the server to process. So, how do I get it to you?

 

[Sysnative Windows Update]

Okay, let's try this differently. Re-do the ProcMon steps, but enable ProcMon as close to the point of failure as you possible can (a minute or two prior to the failing point is okay).

Has the system drive been tested for bad blocks and filesystem corruption?

 

[aalflyguy]

That's exactly what I did. ProcMan failed at 86%. What I have not been able to do is upload the LogFile.zip because of its size. I created this LogFile.zip in both OneDrive and Google Drive. How do I transfer one of those files to you or force it to attach to Sysnative?

 

[Sysnative Windows Update]

Feel free to post the link to OneDrive/GoogleDrive here.

The failing at 86% worries me, but I'll see what I can do.