Announcing Windows 10 Insider Preview Build 15007 for PC and Mobile Insider
-
Oh, crap, Edwin! What's happening? I have to boot twice before I can get to Windows.
Wynona, According to Jenmsft (MS Employee/Engineer) they are aware of the issue and working on a fix. Found it being talked about on their reddit feed. https://www.reddit.com/r/Windows10/c...w_build_15007/
Guess all we can do for now is force boot just hope I don't dent my case too badly
-
-
just found this one on*15007 mobile, have lost the ability to*open apps like time and alarms they wont open
couldn't turn my alarm to not go off at 4am ouch
-
Wynona, According to Jenmsft (MS Employee/Engineer) they are aware of the issue and working on a fix. Found it being talked about on their reddit feed.
https://www.reddit.com/r/Windows10/c...w_build_15007/
Guess all we can do for now is force boot just hope I don't dent my case too badly
Are you talking about my having to boot twice, or Edwin's problem? I went to your link and didn't find anything about booting twice.
-
Booting twice, it was in the thread earlier about 3 to 5 days ago, though the issue was from dual monitor setups the main issue was still the same.
-
-
Just a thought about "Boot twice" - this is the usual behaviour for selecting a non-default GUI BootMenu item (although the second boot is normally automatic)
- are you using the graphical (Metro) boot menu by any chance?
If you switch to the legacy text only boot menu does it boot okay?
Open an elevated prompt and enter:
bcdedit /set default bootmenupolicy legacy
or use EasyBCD, Edit Boot Menu, Menu Options, uncheck Use Metro bootloader and [Save Settings]
Will rebuilding the BCD fix the problem?
-
Just a thought about "Boot twice" - this is the usual behaviour for selecting a non-default GUI BootMenu item (although the second boot is normally automatic)
- are you using the graphical (Metro) boot menu by any chance?
If you switch to the legacy text only boot menu does it boot okay?
Open an elevated prompt and enter:
bcdedit /set default bootmenupolicy legacy
or use EasyBCD, Edit Boot Menu, Menu Options, uncheck Use Metro bootloader and [Save Settings]
Will rebuilding the BCD fix the problem?
Fafhrd used EasyBCD and unchecked Metro as suggested still getting the same having to force a second boot right after login due to the system locking up before it reaches the desktop. It only does this from a cold boot and after a second boot all other restarts are good.
-
Fafhrd used EasyBCD and unchecked Metro as suggested still getting the same having to force a second boot right after login due to the system locking up before it reaches the desktop. It only does this from a cold boot and after a second boot all other restarts are good.
That really sounds like an issue with Fast Boot being enabled on a machine that didn't support it.
I had this exact same issue a year ago until I realized it was fast boot.
-
Yes, disable Fast Boot, and your problem should be solved. If you're booting from SSD Fast Boot is useless anyways.
-
Graphics Problems
Hey guys, has anyone run across any problems with the nVidia GeForce GTX 9xxM's and the 1500x builds?
I have a laptop running the NVIDIA Optimus setup with a GeForce GTX 970M and the Intel 4600. Everything up until the 15002 build worked fine. I didn't notice it at first with 15002, but I knew that when I started the new DOOM (2016), that it just came up with a black screen and the music and stuff was still playing, so I just took it as a problem with the release of 15002 and just moved on. Now that I am running 15007 and am still having the problem, I downloaded Geek3d's GPUTest and attempted to run a benchmark, but was met with a white window for all of the OpenGL tests. I have tried running D3D games and they run fine, I just can't get anything working with OpenGL.
I have removed the driver and PhysX software, and also ran DDU, and manually deleted any leftover NVIDIA Driver folders and registry keys. Installed NVIDIA's 376.33 drivers with no results. I have repeated the drivier cleaning again and am currently running the WIndows Update drivers, but still having the same problem.
Any suggestions?
-
-
Yes, I have heard of this issue all over the place. Maybe better to wait for next release for insiders? A lot of weird stuff going on since 15002.
Funny though is that 15002 was the first build of many where my nVidia 540M actually works at all. At least 5 previous builds could not start the drivers no matter how hard I tried. Interesting is that my old card starts to work and then newer cards start to fail, it used to be the other way around for a long time.
I'd wait for next build as it comes pretty soon, and then we can revisit this topic.