T
tloretz
I had the same problem in my office. By the end of a week of OS 'Upgrades???' (LOL), all of my Window-10 "Fall Creator" version machines were doing the same thing. I found that a massive number of users were experiencing the same problem (or, variations). I fought the problem for 3 weeks, trying every approach offered by MS and tech-bloggers.
It became a Whack-a-Mole. I'd fix a PC and it would self-destruct on the next update push.
Forget about trying to enter SAFE MODE, by pressing F8. MS (in their infinite wisdom) disabled this feature. You can re-enable it. But, you have to find a way to RUN a CMD window as ADMINISTRATOR. Since you're not able to access your desktop, you have to do it outside of the GUI environment. In either case, you must enter the command:
>bcdedit /set {default} bootmenupolicy legacy
(COPY and PASTE without the ">"). This will re-enable the F8 functionality.
However, please READ ON, for another way to get back to your desktop and information you'll need, even if you choose the F8, Safe Mode approach.
I could get machines back up and running, by using a Win-10 ISO DVD, that I created on a working machine. (You can do this too. Find a Windows machine 7, 8 or 10, doesn't matter, that's still working and browse over to MS's "Media Creation Tool" download. It's free. Make sure that you choose to use it to create a WIN-10 ISO DVD. If your machine is Win-10 PRO, then make sure your ISO is PRO, too.
I don't recommend that you choose the 'CLEAN INSTALL' method that is pushed by MS. If you do, you'll get the PC back up in running. But, all of your application software will need to be re-installed, EVEN MSOFFICE. What a pain in the neck that choice was.
After that, I started using the Recovery RESTORE feature. I Restored to a date before the failure mode and the machines got up and running. Not much lost this way. I highly recommend it.
NOW, THE FIX: After you get a machine back up and running, it will want to update to the latest OS version, with all of the latest OS 'fixes'. BEFORE it can download and install and upgrade you must do the following:
1. Open SERVICES (Type the word SERVICES into Cortana and she'll provide you with a Best Match LINK) and change "AppReadiness" to "DISABLED" by double clicking on its ICON. (You'll need to STOP it first, if it's running). Be sure to click on APPLY, before closing the AppReadiness window. Next, CLOSE SERVICES.
2. Go to Windows: SETTINGS > SYSTEM > POWER & SLEEP > ADDITIONAL POWER SETTINGS > "Choose what the Power Button Does" (it's a LINK on the upper left of the window) > Click on the link "Change Settings that are currently unavailable" and DISABLE (uncheck) "Turn on Fast Startup".
The combination of these two changes SHOULD eliminate the BLACK SCREEN with SPINNING CIRCLE of DEATH after MS attempts its next OS upgrade and or 'fix'.
However, if you're using a Logitech wireless mouse and/or wireless keyboard, you may have to disconnect them and replace them with WIRED VERSIONS, or, perhaps, another manufacturer's wireless mouse - keyboard. I had Logitech mice (no wireless keyboards) and I had to go to wired mice to guarantee that the problem disappeared completely. It's some kind of USB problem that seems to be isolated to Logitech wireless devices. Disabling the AppReadiness should take care of this problem, even for Logitech. However, I haven't had time or desire to test this theory. I need to get my office back up and running, productively.
GOOD LUCK!
Continue reading...
It became a Whack-a-Mole. I'd fix a PC and it would self-destruct on the next update push.
Forget about trying to enter SAFE MODE, by pressing F8. MS (in their infinite wisdom) disabled this feature. You can re-enable it. But, you have to find a way to RUN a CMD window as ADMINISTRATOR. Since you're not able to access your desktop, you have to do it outside of the GUI environment. In either case, you must enter the command:
>bcdedit /set {default} bootmenupolicy legacy
(COPY and PASTE without the ">"). This will re-enable the F8 functionality.
However, please READ ON, for another way to get back to your desktop and information you'll need, even if you choose the F8, Safe Mode approach.
I could get machines back up and running, by using a Win-10 ISO DVD, that I created on a working machine. (You can do this too. Find a Windows machine 7, 8 or 10, doesn't matter, that's still working and browse over to MS's "Media Creation Tool" download. It's free. Make sure that you choose to use it to create a WIN-10 ISO DVD. If your machine is Win-10 PRO, then make sure your ISO is PRO, too.
I don't recommend that you choose the 'CLEAN INSTALL' method that is pushed by MS. If you do, you'll get the PC back up in running. But, all of your application software will need to be re-installed, EVEN MSOFFICE. What a pain in the neck that choice was.
After that, I started using the Recovery RESTORE feature. I Restored to a date before the failure mode and the machines got up and running. Not much lost this way. I highly recommend it.
NOW, THE FIX: After you get a machine back up and running, it will want to update to the latest OS version, with all of the latest OS 'fixes'. BEFORE it can download and install and upgrade you must do the following:
1. Open SERVICES (Type the word SERVICES into Cortana and she'll provide you with a Best Match LINK) and change "AppReadiness" to "DISABLED" by double clicking on its ICON. (You'll need to STOP it first, if it's running). Be sure to click on APPLY, before closing the AppReadiness window. Next, CLOSE SERVICES.
2. Go to Windows: SETTINGS > SYSTEM > POWER & SLEEP > ADDITIONAL POWER SETTINGS > "Choose what the Power Button Does" (it's a LINK on the upper left of the window) > Click on the link "Change Settings that are currently unavailable" and DISABLE (uncheck) "Turn on Fast Startup".
The combination of these two changes SHOULD eliminate the BLACK SCREEN with SPINNING CIRCLE of DEATH after MS attempts its next OS upgrade and or 'fix'.
However, if you're using a Logitech wireless mouse and/or wireless keyboard, you may have to disconnect them and replace them with WIRED VERSIONS, or, perhaps, another manufacturer's wireless mouse - keyboard. I had Logitech mice (no wireless keyboards) and I had to go to wired mice to guarantee that the problem disappeared completely. It's some kind of USB problem that seems to be isolated to Logitech wireless devices. Disabling the AppReadiness should take care of this problem, even for Logitech. However, I haven't had time or desire to test this theory. I need to get my office back up and running, productively.
GOOD LUCK!
Continue reading...