Error with Windows Update KB3000850

Hi,

It's really easy to fix it a 800700002 error is a simple OBJCT NAME NOT FOUND ....

for me is just the Accessibility folder who was miss it !

i have juste create a new on into C:\ProgramData\Microsoft\Windows\Start Menu\Programs and the update work fine

for more détails the thread is here :

http://forum.infosub.fr/viewtopic.php?f=9&t=23&sid=ecb82b85cb90e70f3df9fed25a5fbcc0` `

look into you CBS.log

2014-11-25 14:22:12, Error   CSI    00000ed8 (F) STATUS_OBJECT_NAME_NOT_FOUND #14161981# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::OpenFilesystemDirectory(flags = 0, da = (FILE_ALL_ACCESS), dn = [ml:520{260},l:140{70}]"\??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessibility", sa = (FILE_SHARE_READ|FILE_SHARE_DELETE), oo 

bye

Excuse me, but this defies any common sence!

In Windows 8 the standard default location for 'System Tools' folder is actually the 'Program Files' folder. This subfolder is NOT supposed to reside under 'Accessories'. It was moved one level up by Windows 8 (compared to the older versions of Windows).

In fact, back in April we had exactly the same problem with KB2919355 update

http://atarasevich.blogspot.com/2014/04/error-0x80070002-when-installing-new.html

And back then it was caused by the fact that some users moved the 'System Tools' directory from its default Windows 8 location to the more familiar location under 'Accessories'.

Now we are looking at KB3000850, which fails for opposite reason: it actually expects 'System Tools' to reside under 'Accessories'???

What's going on here? Firstly, we have major updates fail just because there was some cosmetic change in menu folder structure?! And now we see that Microsoft cannot make up its mind on what that menu folder structure is supposed ot be?!

For more detail I would use the ReportingEvents.log to get the timestamp.  Then find the portion of CBS.log which corresponded to that.  It might give a clue about which module is "missing".

Hello Robert,

thanks for this great hint!

Checking CBS.log revealed that KB3000850 is picky about the structure of the start menu...

I had moved several entries to a sub-directory:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessibility

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\System Tools

It is easy to spot these errors in CBS.log: search for ", Error" without the quotes (the comma space in front is important).

After recreating these three directories I was able to install KB3000850 :-)

Thanks again & greetings from Germany,

Uwe

Thank you so much!!! I have had a single Windows Update bugging me for over 3 months and it act like it installed just fine, make me restart my computer, and then reappear in the update window when my laptop booted up again. 2 more updates recently started doing the same thing until today.

I created the Accessibility, Accessories, Tablet PC, and System Tools directories (some of them were completely empty), I also created a System Tools directory within \Start Menu\Programs\ and all updates FINALLY installed successfully!! :DDD Such a dumb reason to fail...

Robert,

While the DISM repairs and says things are OK, I still can not load this update.

I tried creating an accessibility folder off my menu, no luck

Any other ideas

I tried creating an accessibility folder off my menu, no luck

Did you check to see if that was necessary?  My suggestion was to use  ReportingEvents.log to find a timestamp and then see if you could find anything interesting and relevant at that time in CBS.log.  Uwe used that suggestion to devise a solution for his case.  What's yours?