I have succumbed to frustration and reinstalled clean from USB ISO. This time on a brand new SSD out the box. Immediately after Windows was finished loading and on the Desktop for the very first time, I ran msConfig and it again shows the startup in Selective and won't let me change it. This with zero programs installed. I also used Express Settings in the install so as not to shut any features off.
Thinking that there must be an issue with Win 10 and my Motherboard maybe unles people actually check this they would not know so it might be an issue that goes unnoticed by most, assuming that I am not the only one. The geolocation service is active at least.
I have finally solved this by clean installing Win10 from a MS DVD. Normal Start up was showing after a clean install. For some reason the USB ISO had issues, even though I Downloaded the ISO twice.
Today i did a full install on a new 2TB hard drive,
after installation msconfig was selected as normal startup.
After few microsoft patch, it became selective startup.
I think it's normal.
If it's really in normal startup but showing as selective, if i click on normal boot it won't ask to reboot comp.
If one service is disabled and i click on normal startup, it will ask to reboot.
Anyway both will comeback to selective mode after a reboot, i think i don't have to worry.
Just to answer GregH question.
Yes, I am also now back in Selective after installing everything and updating. Must be the new "Normal" I did select a few apps to not start at system start but only thru the applications themselves, not the Windows system.
On one of my systems, with W 10 Pro x64 clean install, msconfig always shows Normal, on a second system, upgraded from W7 to W 10, it used to show Selective.
It's a laptop using Ethernet connection so the Bluetooth/Wireless switch is off.
If I do not install a Widcomm Bluetooth driver it shows Selective and under Services there are only Bluetooth Handsfree service and Bluetooth Support service.
Now, if I install the latest Broadcom bluetooth driver, under Services, there is a third Bluetooth related service added, named Bluetooth Service, (running-Auto), and IMMEDIATELY msconfig changes from Selective to Normal by itself. (Even if Bluetooth is not used/enabled.)
Could be another driver/service on your system, but the principle is the same. See below screenshot.
Hope this helps,
Last edited by Vaio 7; 02 Sep 2015 at 09:39.
Ok.... I guess that does make sense. So now how do I work out what driver I am missing when Device Manager shows no errors...
Nothing to do with Device Manager, mine showed no errors before and after Bluetooth sw install.
Of course, if I go to msconfig, section Services and uncheck something, Selective startup is coming back but everything is enabled there.
If you are running your system on Wi-fi connection, open Services and check how many Bluetooth services you have and their status.
I have 3, 2 are not running and the status is Manual (trigger start), and a third called Bluetooth service with status running & Automatic.
If you have Bluetooth sw installed and still on Selective, it's a bit difficult to pinpoint what is the missing driver(s)/services(s).
I gave you one example that worked for me.
In all cases it's a device driver, I do not run my pc with MS W 10 generic drivers, upon upgrade, I updated my Chipset, SATA, Memory Stick, SD and firmware extension parser drivers.
Same for Bluetooth driver.
Same for my Nvidia GPU.
Update: Although my motherboard (ROG Maximus Hero VI) vendor site (Asus) has updated Win 10 drivers, one that they do not have listed for my Board under Win 10 is ASMedia. Under Win 7 I had installed such a driver. So I went and downloaded one from Asus for a later version of my motherboard (Hero VIII) from the Asus website. It installed fine and the Device Manager now correctly identifies the ASMedia controller, not just a generic SATA controller with a MS driver.
After this, MSCONFIG is showing NORMAL STARTUP again. I can only assume that this is not coincidence and that this driver addressed that issue. Happy camper!