New
#380
I've had more trouble using Fast Boot than it's worth. I don't know if it's because I dual boot or not. One of the first things I do with every new build is to turn it off.
I've had more trouble using Fast Boot than it's worth. I don't know if it's because I dual boot or not. One of the first things I do with every new build is to turn it off.
First of all, this last statement - exactly!
I build all of my machines (desktops, anyway) so I am in tune with my hardware almost to the point of being neurotic about hardware drivers as well at OS features that affect driver performance.
I always had an issue with Fast Boot in the original beta builds, but it started working fine close to release. However, last year, as we were ramping up to the April release, I started having these exact issues, and only after a lot of reading did I see someone refer to Fast Boot as being the culprit.
As soon as I disabled it, all my boot issues went away. So I continued to disable Fast boot on every IP build leading up to AU.
After AU, with the numerous clean installs I performed and what not, plus with the hardware upgrades, I stopped turning it off, particularly as I rarely ever reboot, and the OS was finally able to continue to log in as me to complete OS updates. Fast Boot seemed to have started working.
Upon installing 15007, I had so many issues I spent days without rebooting, so it only manifested recently, and I have, once again, turned off Fast Boot.
Well, that is what Fast Boot does - but it does it whether you have a fast SSD (like we do) or a slower mechanical HD. And with it off I still get sub 30 second boot times from power on to log in, so I am not really complaining.
Glad you got it working as well!
That *is* odd. When was your last clean install?
^^^^ This
I never used that, as I have no Samsung drives, so definitely not affecting my machine. In fact, only yesterday did I install the SanDisk SSD manager software, and Crucial's Storage Executive for my SSDs, just to check both. The Crucial had a firmware upgrade, but nothing else out of the ordinary.
It usually needs a UEFI-based machine, which I don't have, hance my turning it off for so long. But for those for whom it works, I day leave it on.
“If it ain't broke....”
My computers are UEFI and Fast Boot still causesproblems. Since Build 15002 if I don't disconnect my HDD before doing the Insider update on my SSD my dual boot gets corrupted and I have to disconnect my SSD and fix the boot sector on myHDD. I'm going to go with drive swapping and do away with my dual booting.
Dona awfully quiet on twitter today, wonder if that means we get a new build.
John,
Last clean install on the insider machine was 3 or 4 builds back. I Started this round with sfc /scannow (was clean) and then went to disabling/uninstalling most if not all of my startups. I Have a dual boot set-up on this system win 10 / win 7 (separate drives) and went so far as to nuke that and rebuild with EasyBCD with and without metro. I was at the point of rolling back and seeing if there was a difference in the builds 14xxx and 15xxx then preforming a clean install with this build when your suggestion worked. I custom build my desktops (for the last 20 years) to the point of being obsessive about what goes in them which is why I have one running the retail branch of win 10 pro and the other running the insider build. I fully suspect there is something MS did that messed with timing on the fast boot but for me it's a non issue with the SSD I just like to know when if something happens that might make it through to the other ( my wife uses that one... happy wife happy life ) For instance crippling Dx9c to use just 4Gb of mem on a 6Gb vid card. She plays a few legacy games and an early change to the drivers in win 10 locked it down, why the dual boot to win 7.
Update: Hint for a new Windows 10 Insider build 15014 soon today.
Tweet
— Twitter API (@user) View on Twitter