Announcing Windows 10 Insider Preview Build 15007 for PC and Mobile Insider

Wynona said:

John, I am pretty sure Fast Boot is enabled on this machine, and hasn't given a problem with any prior Builds. I would think that if Fast Boot hasn't caused an issue before, it shouldn't cause one now.

If I'm not mistaken, I bought this machine with Windows 8.0 on it, and Fast Boot was enabled.

slicendice said:

My computer came with Windows 7, but once Windows 8 came out I never disabled Fast Boot or whatever the name was back then. Once Windows 10 got released, for some builds having Fast Boot enabled caused a lot of issues with pretty much everything. For some builds Fast Boot is no issue. This vary highly from build to build.

Point being, it does not hurt disabling it.

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.

Wynona said:

OK, I'm not one to totally ignore good advice from my betters, although I will argue with them on occasion. [emoji23]

So, I went in and turned off Fast Boot . . . you nailed it, John. That's the pro . . .

The con is that although I have a 540 GB SSD in this puppy, there's no way it boots as fast as with Fast Boot active.

The second pro is that although it doesn't boot quite as fast, I don't have to boot a second time, so maybe I do get going in about the same time frame as with Fast Boot.

Thanks for the hint! It worked!

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!

Helidoc said:

This is the first build I have ever had an issue with fast boot, just turned it off and that took care of it and I have been an insider since before Win 10 was released. I have I second Machine that is Identical to this one that is on the current retail build of win 10 that is not having issues that still has it enabled.. go figure. Thanks for the tip something to add to the troubleshooting routine now.

That *is* odd. When was your last clean install?

Kari said:

I have an Asus laptop that works perfectly well with Fast Boot enabled in UEFI settings, except one thing: When it's enabled, Shut Down leaves the power light on and you can only power on laptop thereafter by first pressing and holding power button down a few seconds to get it really powered down. Selecting Restart will however shut down and power off laptop completely. Normal restart is not possible.

Disabling fast boot, both shut down and restart work normally.

^^^^ This

Cliff S said:

I have had problems previously with fast boot, but when I stopped using Samsung Magicians RAPID MODE, and also doing normal restarts regularly to finish up any PendingFileRenameOperations***, it's been stable and smooth.

   Information

***PendingFileRenameOperations

Stores the names of files to be renamed when the system restarts.
This entry consists of pairs of file names. The file specified in the first item of the pair is renamed to match the second item of the pair. The system adds this entry to the registry when a user or program tries to rename a file that is in use. The file names are stored in the value of this entry until the system is restarted and they are renamed.

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.

Winuser said:

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.

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....”

Winuser said:

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.

Had none of these problems that so many are reporting......Drive swopping is the way to go.

dencal said:

Had none of these problems that so many are reporting......Drive swopping is the way to go.

I don't dual boot, so no real point in drive swapping, and I still had these issues.

Helidoc said:

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.

Sounds like we are in a similar boat, except that I don't dual boot. I keep a laptop around that runs 7, but the other laptop and my desktop are running IP builds.

Update: Hint for a new Windows 10 Insider build 15014 soon today.

Tweet

— Twitter API (@user) View on Twitter