Announcing Windows 10 Insider Preview Build 14267 Insider

Night Hawk said:

Dump a fresh install for the Threshold 2 Update on and then try running the Fast option for the Get insider builds again fresh. You may a hidden problem with the present build you have on being revealed with the failing upgrade attempts?!

Did you remember to unplug any addition drives or devices as well as any unnecessary startups to see if something loading up with Windows is getting in the way?

This is on my laptop. There are no additional drives or devices connected.

I don't see how I can dump the current download for update. It is ready to install again according to windows update but I have defer updates turned on, and fast ring disabled.

Fafhrd said:

I gottasay - why not just post a download link that insiders can access from their telemetered windows 10 installations , instead of this waiting crap.

As they say, "What would be the fun in that?"

Seriously, I think a part of this is testing of update delivery. Could be that the goal is to get to 100% updates with 0% problems. Just a guess, though.

doorules said:

This is on my laptop. There are no additional drives or devices connected.

I don't see how I can dump the current download for update. It is ready to install again according to windows update but I have defer updates turned on, and fast ring disabled.

If you have the BT and WS folders at the root of C which are seen when you see the upgrade is ready to install you can always manually start the upgrade by running the setup.exe if found that is like the two folders on the main build's 10 drive were only seeing the "Sources\Panther" subs in each while the Insider installs having seen upgrades will see one containing all the necessary files.

If the Insider builds seen now following the 10576, 10586 builds were found available for download at the Tech Bench site you would simply mount the iso image for seeing the upgrade take place off of a virtual option drive.

doorules said:

After googling the bluescreen message it basically said driver conflict. But very hard to nail down and diagnose.

I went into control panel, programs, and simply uninstalled just about everything there. Just left chrome installed and Intel graphics.

Install then went through without problems.

Fafhrd said:

I gottasay - why not just post a download link that insiders can access from their telemetered windows 10 installations , instead of this waiting crap.

BSODs are generally driver issues to begin with so dumping video and sound drivers are often the cure when the wrong ones end up going on or need to be reinstalled all over again. The msconfig utility is a fast option to use when not wanting to strip all the programs way but simply have everything disabled at first in order to enable only one or two startups at a time. That's always been a common method for debugging things by being able to identify the one or two things causing the problem.

Of course with the changes seen in 8 to the Taak Manager you can also disable almost everything in the Startup tab there as well. When going to upgrade 10 on one older 7 laptop which I knew would need a clean install right away to follow I ended with 8.1 drivers and there will never be any for 10. If you model is 4-5yrs. old before 8 was even out expect there will be none for 10 anyways. Some have to go to the manufacturer's support site to grab 8.1 drivers instead.

Well time to leave... the main build's host drive's 10 Pro Threshold 2 Update that is and reboot into 7 for a look at the 10 Pro VM there to see how things are going. That never saw the 11092 even after the 10568 Insider went on. Now to see if that will get this one.

Update: When finding both 10 Pro VMs one named 10 Pro x64 and the first Windows 10 x64 being set aside for Insider builds the 10 Pro x64 was latest set to get them since that had been the TH2 iso used for it while the other was the 10565 upgraded to 10576 to 10586 in progression as the TH2 and is presently just having seen the exact same four updates go on while the 10 Pro x64 is downloading the 14267 build when seeing that started about an hour after the first.



As you can see the resolution is higher at 1600x844 on the second 20" lcd which replaced the second 19" lately to allow more screen space between two machines as well as multiple VMs on both. Had to shut down the first on the left however and wait until all updates go on before the last being the 14267 build go as seen before!

blackroseMD1 said:

Well, gamed a lot tonight with just one hang so I hoped the issue was somewhat resolved. After I was done gaming and was just browsing the web a bit, the mouse thing happened again. At this point, I guess I'm just going to go back to 11099 and move to the slow ring.



That seems to be the errors that show up in Event Viewer each time the mouse stops responding. It's gibberish to me, but hopefully one of you more enlightened folks can make some sense of it.

Have you tried using an "Old fashioned" nothing special, basic mouse?
Of course that's not the answer(Win10 should work with it, but it could be your mouse's drivers), but it's troubleshooting.