Windows 10: Fall Creators Update Causing Issues

You want the next one down. "Go back to the previous version....."

The process is the same whether you update or use key. Key just means you download once. It is said that is goes faster. I've never tested with stop watch but I do believe it is quicker. (the download seems to run smoother.)

What ever you are comfortable with just no resets, just "Go back"

 

Ok, thank you, so just go back to the previous version. That's what I thought. I got confused because you suggested the Media Creation Tool, and from what I see when I read the information about it, that reinstalls Windows, which would be like resetting?

 

Sorry. No first you go back. Then when you want to try again you use the media creation tool to create a USB key.

This key is multi purpose. If you boot from it you can clean install or use some basic tools to "Fix" windows. Handy is an emergency.

If you navigate to key and double click setup then it does a repair / upgrade. If the version you are running is same as key it repairs, if the version you repairing is older it upgrades.

I always recommend in very loud font, do a Back Up. This is an OS upgrade.

 

Ok, thanks for that clarification, but I was under the impression that if you revert back, then you're just back where you were, therefore you can just reinstall the update again by manually checking in Windows or downloading it from the top of the same Microsoft page where the Media Creation Tool is at.

 

Yes you can do that.

Having the key means you download once, maybe it doesn't work again, and you have bootable media for emergencies.

 

Hi Ken, before I reverted back, I wanted to do a little more research into this (Googled it), and I found a post on another forum where this guy was having the same issue as me. There was a forum member who issued him this advice:





This lets you choose options in a 'Local Group Policy Editor' window. I followed these instructions, and did a quick shutdown and restart, because if it didn't work on a quick shutdown and power button startup, it definitely wouldn't work in a long one, which is when my issue always occurs.

Well, it didn't work as planned, and Windows chose another lockscreen/logon screen image for me, other than the other wrong image it's been choosing (it selected a second wrong image, so it was actually worse lol). I noticed also that by going into Windows' settings to change the lockscreen, the option was grayed out, hence the actual result of these directions, if you think about it (it disables the option to choose one, even manually). I then went back in and disabled it so I could manually choose my own image again.

However, another option in the 'Local Group Policy Editor' window caught my eye, and I said to myself, this just might work. It's the one highlighted below:





So by choosing to force a specific default lockscreen and logon image, it lets you insert the targeted path in Windows to the image. So I then searched Google images for the exact lockscreen image I had chose in my system settings, before I had this issue (the one that SHOULD be displaying). It's the one looking out of a small airplane, showing a red airplane wing in the foreground, and the blue ocean down below. I was able to locate a large, high-resolution copy of this image, so I saved it to a specific folder in my computer. I then copied the path of the image, and inserted it in the edit section of the option you see highlighted above (right click, then choose 'edit' to proceed).

I performed a quick shutdown, and powerup again, and the image appeared. However, that doesn't solve the issue right away since this glitch only happens after a long shutdown. The next morning when I powered-up my computer after several hours of it being off, not only did the proper image appear, but my computer booted up very quickly (no pausing, or 'Please Wait' screen or anything). It booted up just as normal, before the Fall Creators Update changed things. This apparently fixed it, or I should say it's a perfect work-around to this glitch.

So evidently, the slow startup occurring after selecting to proceed using Windows instead of System Restore (prior to the lockscreen/logon screen), is related to Windows trying to process this glitch of choosing between the selected/desired lockscreen image in your settings, and the one that it decides to revert to by itself. By forcing a new and different pathway to a desired lockscreen/logon image, bypasses the original process, and it goes right to it.

I will continue to monitor this situation, since I just implemented this current work-around solution. But I can almost bet to say with full certainty, that it's going to continue to work, because since the last big Windows update, this glitch has happened EVERY single time like clockwork after a long shutdown, and this time it did not. I'll let you know in a couple of more days if this continues to work. If so, then you can offer my situation as a work-around solution to this issue, for anyone else who experiences it, as well.

Thanks again for all of your help, I actually learned a lot from the things you gave me, especially if I ever need to reinstall/repair Windows, or revert back to an earlier version. There were a lot of things about that which I didn't know, but now I do.

~FGN

 

Excellent. Great information and good detail. Thanks for sharing.

 

Hi Ken, unfortunately that workaround didn't resolve the issue, because it reverted back to doing the same thing again. So I then went back and disabled that change in the gpedit window (the ones I described in my last post), and switched back to normal mode of selecting a lockscreen image through the regular Windows settings. Since then, the same problem of the incorrect lockscreen image and slow start-up continued after a long shut-down.

But yesterday when I powered off my computer, I noticed that Windows said that it was installing updates during the process, which did not take long, but did not restart automatically to complete (maybe it didn't need to). I decided to just powerup the computer again anyway, and after logging in, it went to a 'Windows is preparing Features' message, or something like that, and then to my desktop like normal. Once my computer booted up totally, I then shut it down for the night again.

Today when I powered it up after several hours of it being off, which is when this lockscreen issue happens, it went right to the correct lockscreen image, which surprised me. In addition, there was no 'Please Wait' screen or slow startup like usual. What I'm starting to think is that small update yesterday during the shut-down process, was an update Windows made to correct this lockscreen image issue.

I hope I'm not speaking too soon, because I have not shut down my computer since, and experienced a long period between turning it back on, but it only seems logical because it has not selected the correct image after a long shut-down since the Fall Creators Update, which was all the way back on 11/15. The only time it selected the correct image is when I applied that gpedit change in my last post, but when the same issue resurfaced again, I went back and reversed those changes, like I said. I will definitely let you know either way, so I hope it was indeed a fix by Microsoft for this issue.

 

Thanks for update. The mysteries of Windows.