Update...
I found what the heck is going on...
Looks like the 1709 update set windows 10 to fast boot.
Which in my case, It's decision time.
Do I leave it on and use shut down only and have no errors, and loose access to legacy bios and being able to boot to safe mode using my delete key.
Do I turn it off and have the errors but have access legacy bios hitting my delete key and enter safe mode by hitting f8.
I think the errors are going to stay...
In your BIOS, do you have the option to have both selected. I do on my Gigabyte mobo....I have 3 options....UEFI, Legacy, UEFI w/Legacy....which is what I use.
To your question: That depends on your needs. Do you need to go and change the boot order all the time and boot from USB. If not...go with UEFI. Otherwise go with Legacy.
I would make the same choice. When fast startup is enabled, you don't get errors because when you power on your machine the system is just resumed with services already started, but the error is still there and WAS is off.
I hate fast startup actually, since I've seen it bring problems but never solve any, and I've never seen anyone complaining like "The boot process seems sooo slow, now that fast startup is disabled"...
Reply to Plankton & NovHak ...
Plankton, My board is a bit long on the tooth (AsRock 890FX Deluxe 4). No UEFI support...
NovHak, I'll keep digging to see if I can find the problem as to why (WAS) will not start. If I can make it run most or all of the errors I'm getting should disappear. I have never used fast boot, This PC boots up in around 20 seconds so that fine with me...
However when the update activated fast boot it was booting up in about ten seconds, it was fun to watch it boot up so quick while it lasted... LOL...
Finally found the problem...Looks like the 1709 update for some reason enabled FTP. I Disabled it.
It also enabled Windows Process Activation Service (WAS).
I also disabled Windows Process Activation Service (WAS).
This removed all the errors caused by (WAS)...
When Searching the net looking looking for information on how to fix (WAS) errors.
I ran across a post that said that Windows Process Activation Service (WAS) has nothing to do with windows product activation.
I also found another post that said FTP and Windows Process Activation Service (WAS) in windows are disabled by default, found in "Turn Windows Features On of Off".
Just thought I'd post this in case someone was dealing with the error caused by (WAS)...
@Raner - Windows has a very bad habit of resetting a lot settings in your PC, you have to go thru all your settings
to check and set it right again! System restore will be turn off after version upgrade (1607/1703/1709) and
have to be turned ON again, also check your Power configuration (Advanced one), that's also messed with.
Sometimes you will find a program that used to work ok, but now don't! The solution is often to uninstall and
then reinstall, reboot and then it will work as it used to.
Settings and functions are removed without any warning or info, that is the "price" of Windows as a service!
Thank you Raner. You solved my computer issues about NOT using restart but only using shut down. Happy New Year. Greg
Quote
