DavidNist - I am interested in your fix please
HI Gillian -
So I don't walk you down a non-applicable path, can you relay what screens win10 presents you with during bootup?
After logging on and waiting for what feels like an eternity, does the sequence finish with a black screen, an unresponsive start bar, and a *"Desktop
is not accessible. Access is Denied?" popup?
If yes, then depending on what actions you've already taken, I may be able to help. This recipe is non-destructive, but it may be too late if you've tried any of the more intrusive fixes other threads have recommended. The best hope, in that case, is file
retrieval and an OS refresh.
Is your goal to restore the box to pre-update condition or are you trying to save your data files before reinstallation?
Regardless what you've read in other threads, this very specific "Desktop is not accessible" foul up is permissions based, related to the temporary storage location win10 uses while the update is running under certain legacy hardware configurations. The
idea for the update is to convince the OS the 'logged in' user has permissions to run the update file by file, then move those temporary perms back with the files to their original locations, restore hardware state then finally finishing things up with a restart
without any user intervention.
That's a pretty tall order for a little 100.00 (or free) operating system to pull off successfully each and every time an update is released. I can only imagine the difficulty the OS team has in keeping with every single hardware iteration ever made with
the "Windows 10' logo.
Not required, but handy items before we start:
- USB drive (errors out with anything less than 32gb)
- media creation tool
- win10 physical media
Expect a two-hour gig. It's easy to forget what comes next while sitting and waiting 7-10 minutes before a 'next action' occurs in the sequence, so it's a good idea to keep pencil and scratch paper handy to track your progress.
lemme know if this is something you'd like to run with.
all good success.
David
*apologies in advance for the quality of the screen caps and lack of detail in the link. I'll have a complete write-up over there as soon as time permits.
**For some reason, I'm unable to post images inline here. The provided link is for a new site I'm producing that is definitely NOT ready for prime-time yet.