The Hotfix Share

Welcome Guest ( Log In | Register )

3 Pages V  < 1 2 3  
Reply to this topicStart new topic
 kb2919355 Component Store corruption, Windows 8.1 / Server 2012 R2 April 2014 update
xable
post May 20 2014, 09:12 PM
Post #21





Group: Administrator
Posts: 3,052
Joined: 27-May 06
Member No.: 1



That's good news, thanks for the update.
Go to the top of the page
 
+
RonnieJP
post May 21 2014, 07:14 PM
Post #22





Group: Hotfixer
Posts: 11
Joined: 21-April 14
Member No.: 97,650



QUOTE (cgthamm @ May 20 2014, 07:45 AM) *
My support case has reached the point where "we are now waiting for Microsoft to release a new update."

Let's hope Microsoft gets it right with first release of the update...

I ended up doing an inplace repair install from a Windows 8.1 ISO download and was able to successfully install all the updates (including KB2919355) without any corruption to the component store. I was able to run disk cleanup with system files, including previous Windows installations and Windows update files. Afterwards, I was able to run all the DISM cleanup-image commands without error. So, I hope this alleged "new update" doesn't break things again!
Go to the top of the page
 
+
cgthamm
post May 31 2014, 06:27 PM
Post #23





Group: Hotfixer
Posts: 78
Joined: 25-September 07
Member No.: 6,596



I received another call about this support case from someone in Product Development. After a brief discussion, he basically said I (and, by extension, others with this problem) may have to re-format.

Here are the scenarios as I currently understand them.

1. If you A) do not yet have kb2919355 installed (because, say, you refused to install it from Windows Update or it did not install successfully); and B) are unable to successfully run dism /online /cleanup-image /restorehealth, then you will likely have to re-format, regardless of the fix Microsoft will be releasing.

2. If you installed kb2919355 and cannot uninstall it, you will also likely have to re-format.

3. If you installed kb2919355, are able to successfully uninstall it, and then successfully run dism /online /cleanup-image /startcomponentcleanup , then you will likely NOT have to re-format.

Incidentally, he also said that this problem affects a lot of people, although he didn't elaborate as to how many. He did say, however, that many others are unable to install kb2919355 in the first place.

This post has been edited by cgthamm: May 31 2014, 06:31 PM
Go to the top of the page
 
+
RonnieJP
post May 31 2014, 08:51 PM
Post #24





Group: Hotfixer
Posts: 11
Joined: 21-April 14
Member No.: 97,650



QUOTE (cgthamm @ May 31 2014, 11:27 AM) *
I received another call about this support case from someone in Product Development. After a brief discussion, he basically said I (and, by extension, others with this problem) may have to re-format.

Here are the scenarios as I currently understand them.

1. If you A) do not yet have kb2919355 installed (because, say, you refused to install it from Windows Update or it did not install successfully); and cool.gif are unable to successfully run dism /online /cleanup-image /restorehealth, then you will likely have to re-format, regardless of the fix Microsoft will be releasing.

2. If you installed kb2919355 and cannot uninstall it, you will also likely have to re-format.

3. If you installed kb2919355, are able to successfully uninstall it, and then successfully run dism /online /cleanup-image /startcomponentcleanup , then you will likely NOT have to re-format.

Incidentally, he also said that this problem affects a lot of people, although he didn't elaborate as to how many. He did say, however, that many others are unable to install kb2919355 in the first place.

Thanks for posting this cgthamm. It boggles my mind how MS can so casually tell us to reformat. Don't they have a clue as to how time consuming this can be? Especially finding and reinstalling all of a user's programs and their key codes. They do not even appear to admit any culpability, let alone an apology or some compensation. It's unbelievable! There is no doubt in my mind that this whole issue was precipitated by the update. When I restored my system from a pre-update disk image for testing, I had no problem running DISM /online /cleanup-image /startcomponentcleanup without any errors. When I did the inplace re-install it was over the updated image (that had the DISM issue) and everything now works fine, including all the DISM commands. So, I'm not so sure that a complete reformat is always necessary.
Go to the top of the page
 
+
cgthamm
post Jun 11 2014, 01:03 AM
Post #25





Group: Hotfixer
Posts: 78
Joined: 25-September 07
Member No.: 6,596



Just a quick note to say that I have just installed June's Windows Updates (as well as some of the publicly available hotfixes) on my Windows 8.1 laptop, and am now able to run the following sequence of commands (in order) with no errors:

dism /online /cleanup-image /restorehealth
dism /online /cleanup-image /startcomponentcleanup
dism /online /cleanup-image /scanhealth

This is the first time since installing kb2919355 that this has been true. Thank you to all who helped make this happen. I will try to find out specifically which update fixed the problem and post what I learn here.

In the meantime, if you have been unable to install kb2919355, have a look at the following Knowledge Base article:

KB2966870 - Fix restart problems after you install update rollup 2919355 in Windows 8.1 or Windows Server 2012 R2

I will also be re-testing my recipes for all the other bugs I've been forwarding to Anthony Bartolo at Microsoft Canada. It would be a most welcome improvement if they could finally get desktop windows to stop spontaneously changing their z-order...

This post has been edited by cgthamm: Jun 11 2014, 01:30 AM
Go to the top of the page
 
+
RonnieJP
post Jun 11 2014, 06:54 PM
Post #26





Group: Hotfixer
Posts: 11
Joined: 21-April 14
Member No.: 97,650



Before I installed yesterday's updates, I looked at the Knowledge Base articles for each one. I noticed that one of the updates KB2969339 was "allegedly" to fix an issue "Error 0x80073712 when you install update 2919355 in Windows 8.1 or Windows Server 2012 R2". It said This issue occurs because a new component in update 2919355 contains a file version that is later than the file version that was already installed on the computer and that Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Of course it said nothing about the DISM issues, but here is the link to the article: http://support.microsoft.com/kb/2969339http://support.microsoft.com/kb/2969339 Several users on a Microsoft forum http://answers.microsoft.com/en-us/windows...e85e7bc3?page=8 are reporting that this was the update that fixed the problem.
Go to the top of the page
 
+
cgthamm
post Jun 19 2014, 08:32 PM
Post #27





Group: Hotfixer
Posts: 78
Joined: 25-September 07
Member No.: 6,596



You're right, RonnieJP. The update that takes care of this problem is:

KB2969339 - Error 0x80073712 when you install update 2919355 in Windows 8.1 or Windows Server 2012 R2

It is available from the Microsoft Download Center and from Windows Update.

NOW, Microsoft, how about fixing the spontaneous window z-order changing? Or the networking -- specifically SMB file sharing, and wireless networking? Also, "connected standby" and the other Draconian power management changes are way more trouble than they're worth -- let people choose to turn them off without sacrificing functionality or stability.

This post has been edited by cgthamm: Jun 19 2014, 08:40 PM
Go to the top of the page
 
+
NoSubstitute
post Apr 6 2015, 06:54 PM
Post #28





Group: Hotfixer
Posts: 3
Joined: 6-April 15
Member No.: 97,905



QUOTE (RonnieJP @ Jun 11 2014, 08:54 PM) *
... Several users on a Microsoft forum ... are reporting that this was the update that fixed the problem.


QUOTE (cgthamm @ Jun 19 2014, 10:32 PM) *
You're right, RonnieJP. The update that takes care of this problem is:
...

Sadly, this is still an issue.
Turns out I already had the KB2969339 update installed, but not the KB2966870 one. Installed it, but it didn't help me either.

I've included lots of dism logs over here.

My major grief right now is that I can't seem to do the Repair Install either. :-(
The setup only runs for a few seconds "Preparing xx%", up to 100%, then it dies, without error messages.

My Windows Installer has been broken forever, it seems, and there are a couple of MS Office updates that refuse to install. (Error code 800070641.)
And, of course the superlarge 3000850, which is supposed to be a non-critical update. It never installs correctly.
Go to the top of the page
 
+
NoSubstitute
post Apr 7 2015, 05:28 AM
Post #29





Group: Hotfixer
Posts: 3
Joined: 6-April 15
Member No.: 97,905



QUOTE (NoSubstitute @ Apr 6 2015, 08:54 PM) *
...

My Windows Installer has been broken forever, it seems, and there are a couple of MS Office updates that refuse to install. (Error code 800070641.)
And, of course the superlarge 3000850, which is supposed to be a non-critical update. It never installs correctly.

3000850 comes back with the error 80073712, which suggests I run DISM. :-)
Go to the top of the page
 
+
NoSubstitute
post Apr 22 2015, 07:01 PM
Post #30





Group: Hotfixer
Posts: 3
Joined: 6-April 15
Member No.: 97,905



FIXED IT!
No suggestion anywhere helped me.
Instead I can tell you that I have fixed one of my errors myself, by manually replacing the MSI files from the Windows 8.1 Pro ESD USB stick. That was unnecessarily complex, but it now means that my Windows Installer starts!

I have tested to install some small programs and installing those Windows Updates that have refused to install for months. Both worked. I'm soon going to reboot the system for the first time since the fix and will comment about future issues in this thread.
Go to the top of the page
 
+

3 Pages V  < 1 2 3
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 19th September 2019 - 01:18 PM
All trademarks mentioned on this page are the property of their respective owners
The Hotfix Share is not affiliated with Microsoft
Copyright © 2019 TheHotfixShare.net