|
Welcome to the Grumpy Old Farts Club, David.
Software Zen: delete this;
|
|
|
|
|
Been there for a while, I'm afraid.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
You do know what error 0x80070002 is?
It is the Windows error code 2 (ERROR_FILE_NOT_FOUND, "The system cannot find the file specified") mapped to a HRESULT.
|
|
|
|
|
My desktop and the WookieTab are both on 1803 (OS Build 17134.112) and updated without any problems - indeed on the WookieTab is was actually better than the previous version (the soft keyboard actually works instead of spending all it's time annoying me).
And I've yet to see a single BSOD since the update.
Could be that I have nice, "standard" hardware - if there is such a thing - but I doubt it, particularly with the WookieTab which being Chinese could be partially made of egg noodles for all I know ...
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Ditto for my Wook - although I have put a professional version on it
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
Another "no-help" reply, I'm afraid: no problems here upgrading three different PCs.
Have you tried using the Media Creation Tool[^]? With previous updates, it's sometimes done the trick for me when Windows Update kept failing.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Hi,
I would recommend opening PowerShell and using: Get-WindowsUpdateLog [^]
That should help you find the source of the 0x80070002 HRESULT error.
Best Wishes,
-David Delaune
|
|
|
|
|
Since Microsoft makes it rather non-obvious how to find out what version of Windows I'm running (doing the obvious, "This PC -> Properties" doesn't tell me) I have no clue what version I'm running.
I know y'all have told me how to find out, but since it's non-intuitive and I didn't write it down, I don't remember! 
|
|
|
|
|
WINKEY+R, "winver", ENTER.
And the stupid dialog that pops up won't let you copy the text ... 
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Even shorter - WINKEY, "winver", ENTER.
Kevin
|
|
|
|
|
winkey? as in half of a purple teletubbie?
or perhaps you missed the undersized spacebar?
me: guilty of too often not using use the shiftkey.
tip of the day for north americans: keep your drinks cool in the esckey.
alternative 2: from a Benny Hill Asian impression: winkey winkey nudgey nudgey...
This internet thing is amazing! Letting people use it: worst idea ever!
|
|
|
|
|
I just checked, and 1803 is the build I'm showing. (installed 5/24) I should also mention that this workstation had some minor issues that made me revert to a previous restore point...which created major issues, leading to the migration to a newer workstation I had 'waiting in the wings'. Today though, I'm working on the old system (waiting on a sound card for the new system) and it seems almost normal...almost everything works even though many of the programs don't show up in 'programs and features'. I can't say I've seen anything with this update that seems noteworthy other than it seems to break stuff...but not everywhere...my other two Win10 systems have no negative side effects. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
I am going through a similar issue, but for me the error code is
0xc1900104 .
Reading through various boards gleaned very little, but on one there was mention of making sure you have the latest NVidia graphics drivers installed, so I am trying that right now.
Will try that Powershell script if it fails again.
UPDATE:
Most peculiar. After updating the NVidia driver, I was able to perform the full update. Had to do a couple of restarts manually. After that.... it reports that the update failed. And of course it started downloading the update yet again... 
modified 16-Jun-18 11:05am.
|
|
|
|
|
Post this as a tip/trick for other users?
|
|
|
|
|
Yes that update really sucks. It requires a ton of space. Have not bothered with it since it will not install because of space, and my SSD does not have enough to spare unless I uninstall almost everything. May get around to doing it, or replacing the SSD.
|
|
|
|
|
I've found it virtually impossible to update to that version.
Probably because I don't have a WIN10 machine.*
* Required Answer For Thread
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
BillWoodruff wrote: DISM.exe /Online /Cleanup-image /Restorehealth
If only that worked for terminally ill people! 
|
|
|
|
|
This worked for me! Thanks Bill...
|
|
|
|
|
What causes this is a corrupted registry key in the HKEY_LOCAL_MACHINE hive. Unfortunately even if you get past this on the current upgrade you'll have the same issue on the next one. Your best option is to do a clean install from a bootable DVD or USB drive.
|
|
|
|
|
Have you checked out Microsoft lately?
... such stuff as dreams are made on
|
|
|
|
|
You utter git.
This space for rent
|
|
|
|
|
Cue irrelevant side comment:
Source control for bovines: You udder git.
Software Zen: delete this;
|
|
|
|
|
Git outta' here!
It was broke, so I fixed it.
|
|
|
|
|
|
it just led to conflicts with my pending chances
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
