Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Windows 8.1 KB2919355 update fails


  • Please log in to reply

#76
woodrow896

woodrow896

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 128 posts

I spent an hour and a half on this with an HP tech and he did everything and could not figure it out. We could make the problem happen and restart windows explorer and it would happen again each time just one time then be good for the duration until we restarted the machine or explorer and it would do it again one time. The tech admitted at the end he was aware of the KB2919355 update and there are problems with it...well...DUH !  LOL  


  • 0

Advertisements


#77
JW0914

JW0914

    New Member

  • Member
  • Pip
  • 2 posts

Part 1 of Repair Process

 

The following fixes the Component Store Corruption KB2919355 AND Windows Update causes...

 

The following DISM commands must be given in the chronological sequential order of:

 

First

(Fixes Component Store Corruption; Should 1 or 2 fail with an error, rerun. If either fails a second time, you will need to do a repair install, see tutorial at bottom):
1. dism /online /cleanup-image /startcomponentcleanup
2. dism /online /cleanup-image /restorehealth
3. Restart
4. sfc /scannow
5. Restart

 

Second:

("Resets" Windows Update; however, if you attempt KB2919355 again through Windows Update, the same corruption will occur again)

1. Create bat and run as ADMIN:

 

net stop wuauserv
rmdir /s /q C:\Windows\SoftwareDistribution\DataStore
rmdir /s /q C:\Windows\SoftwareDistribution\Download
net start wuauserv

 

2. Restart

 

Warning: this was not a fast process... component cleanup took almost 5 hours. 

 

Advice: 

If the above fails to get rid of the Component Store Corruption (steps 1 or 2 fail), then an install repair (upgrade to your same version of windows) will be required.  Although this repair does not eliminate the corruption, if you're unable to fix the corruption using the method above. then the install repair is replacing something that is needed to fix the corruption but which is not able to provide a fix on it's own. Also, download [search] "Microsoft Safety Scanner" from the Microsoft website (I apologize, as I don't remember the thread I found the link on) and run it in full mode either way.

 

Tutorial for Repair Install "upgrade"

http://www.eightforu...indows-8-a.html

  • Once KB2919355 causes corruption to the extent that /restorehealth no longer operates without errors, there is nothing further than can be done to repair the corruption, except a Repair Install.  DISM /restorehealth was designed to fix component store corruption and is the only application able to do so. Windows Update and KB2919355 causes system corruption to such an extent that using /source and pointing to the installation media or a working windows 8 installtion without corruption does nothing and /restorehealth still fails.

 

DO NOT, I REPEAT, DO NOT REFRESH/RESET YOUR PC.

 

DISCLAIMER:
Microsoft will deny this update caused corruption within end user's systems and will blame it on everything else but components of their own OS, most especially Windows Update.  The only problem with this: thousands of users have reported massive corruption not only to the Component Store, but also within the DISM and System File Checker utilities.  Microsoft closed the two longest running threads on the corruption caused by KB2919355, one 116 pages long, the other 103... all the while telling users to run /scanhealth /restorehealth maybe a /startcomponentrepair in their somewhere, but never in the order which they must be run, or how to explain DISM /restorehealth corruption errors when being used with /source and the source was a mounted install.wim, as well as a VM win 8.1 with no corruption within it's component store.  
 
 
Part 2 of Repair
 

Fix that WILL allow the install of KB2919355

 

As many discoveries have been made, I discovered this accidentally. and quite by coincidence... 

 

In order for users, who've been plagued by errors and file corruption, to get a successful completion of KB2919355, all that's needed is to run the 8.1 upgrade installer, and when the 8.1 installer goes to the wait screen after entering the generic product key, start Windows Update for the install of KB2919355

 

EDIT: It appears, from the input of other users, one must FIRST install the 5 standalone updates included within the Windows Update KB2919355 package, you will then need to restart after the fifth and final standalone, then use Windows Update to install KB2919355 (do not use the standalone installer for KB2919355... use Windows Update).

 

Steps

  1. Run the Windows 8.1 installer from within Windows, as if you're going to do an install repair "upgrade".
  2. Enter the generic product key, and upon clicking next, the installer will say wait... 
  3. Give the installer about 5 minutes, then start Windows Update (it should show the KB2919355 update), and click install.
  4. Windows Update will begin downloading the update... if you have a Windows Update cache problem that causes the speed and percentage to remain at zero, don't worry about it and get the update installed first, then you can clear the cache and remove the directories afterwards.
  5. The install may fail, don't worry... simply hit install again, making sure the 8.1 installer screen is still on the "wait" screen, as whatever the installer is doing during the "wait" screen is what makes the KB2919355 install possible. 
  6. KB2919355 should install and Windows Update should request you to restart... simply do so without cancelling the 8.1 installer.  Windows will finalize the update during the shutdown and restart processes.
  7. Upon rebooting into Windows, you will have a multitude of additional updates that will need to be installed (around 10, give or take a few), and you can verify the install of KB2919355 by going to "view installed updates" 
 

 

 

 

 


  • 0

#78
woodrow896

woodrow896

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 128 posts

OK I did this part and all was well with SFC scannow before and after and scanhealth was good before. Didn't check that after. .

First

(Fixes Component Store Corruption; Should 1 or 2 fail with an error, rerun. If either fails a second time, you will need to do a repair install, see tutorial at bottom):
1. dism /online /cleanup-image /startcomponentcleanup
2. dism /online /cleanup-image /restorehealth
3. Restart
4. sfc /scannow
5. Restart

 

Machine runs great with the KB2919355 update except the second folder I try to open goes into the twirling circle or hour glass for 45 seconds or whatever it is then opens, then every folder after that opens fine.

Thanks


  • 0

#79
woodrow896

woodrow896

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 128 posts

So, in other words...nothing has changed. Still the same annoying folder problem.

Thanks


  • 0

#80
woodrow896

woodrow896

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 128 posts

I am happy to report that Microsoft optional update KB2962409 solved the folder going into wait mode problem. It was a Skydrive/Onedrive issue. Prior to installing this update another guy suggested that I take out the Skydrive data I found in a registry key in User Shell folders and it worked. Then, I put the data back in when the optional update came out and the problem never re-occured so I am good on that.

 

The ONLY other issue I have now with windows 8.1 is the fan runs full speed and sometimes toggles on and off for a couple of minutes after a cold start up. Never did this before.

 

I replaced the video drivers a couple times with older and newer versions but that does not help. It has been suggested that could be the culprit.

 

Thanks for any ideas.


  • 0

#81
woodrow896

woodrow896

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 128 posts

On a hot restart or if the machine is turned off and restarted a few minutes later the fan works normally, you never hear it unless you are consuming resources like starting a virus scan.

Just on a stone cold startup the problem exists.


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP