Windows 10 Insider Preview Build 17101 Fast + 17604 Skip Ahead Feb. 14 Insider

BugMeister · 21 Feb 2018

- further clarification of the Ultimate Performance mode..

CountMike · 21 Feb 2018

And reason not to give everybody a chance at it would be ????

magilla · 21 Feb 2018

Brink said:

Update: New "Known Issue" added.

Thanks @Brink for posting this. At least those of us who have this problem don't feel like we are really out to lunch! I resolved the problem on 3 of my systems but on one of them, when I turn off fast start, stranger things happen than when I leave it on. So, I'll be content to know others are in the same boat. The system I have trouble with is an AMD system and it is running the SKIP AHEAD.

cereberus · 21 Feb 2018

johngalt said:

I take it you like Being Erica....

Not really sure where that came from (look back at your post, and my quote in it - that certainly was not there in my original reply) lol, but I'll have to assume it was you that put it there....

And also, my original reply had 64 Boldfaced - but it doesn't show up easily on some of the styles here for the forum software.

Weird - never heard of Being Erica (never been shown in UK afaik) before but stumbled across it in a website and watched it for first time YESTERDAY!

Sort of like Quantum Leap except she sorts her own issues.

Wynona · 21 Feb 2018

magilla said:

Thanks @Brink for posting this. At least those of us who have this problem don't feel like we are really out to lunch! I resolved the problem on 3 of my systems but on one of them, when I turn off fast start, stranger things happen than when I leave it on. So, I'll be content to know others are in the same boat. The system I have trouble with is an AMD system and it is running the SKIP AHEAD.

I have an AMD system, Magilla, and it works on it. So, for the record, it's not AMD this time. :)

magilla · 21 Feb 2018

Wynona said:

I have an AMD system, Magilla, and it works on it. So, for the record, it's not AMD this time. :)

I have one AMD with 17101 on it and your solution works. This AMD has 17604 on it and nothing works! My two Intel computers work with your solution, also. They also have 17101 on them. Seems like 17604 - at least for me - has a problem different from 17101.

Wynona · 21 Feb 2018

magilla said:

I have one AMD with 17101 on it and your solution works. This AMD has 17604 on it and nothing works! My two Intel computers work with your solution, also. They also have 17101 on them. Seems like 17604 - at least for me - has a problem different from 17101.

Hmmmm, I pulled out of Skippy not long after I joined, so I don't have a clue.

I will say, though, that for the number of posts about no-boot (only about 30 to 35), I'm surprised Microsoft jumped on the issue so quickly.

The only thing I can think of is that I saw Jeremy's feedback, tried it and it worked for me. I think I posted some four or five times on the issue and I think I even said that it worked for some at TenForums. Maybe that did the trick? Who knows ...

larc919 · 21 Feb 2018

Wynona said:

Hmmmm, I pulled out of Skippy not long after I joined, so I don't have a clue.

I have 1 on regular (17101) and 1 on Skippy (17604). Both Intel CPU with fast boot turned off. No particular problems with either that I've found so far. Skippy wouldn't let Windows Defender update at the start, but that somehow sorted itself out.

f14tomcat · 21 Feb 2018

Double-triple talk. Could mean anything, but enticing!

Tweet
— Twitter API (@user) View on Twitter

Windows 10 Insider Preview Build 17101 Fast + 17604 Skip Ahead Feb. 14-2018-02-21_18h36_06.png

linw · 21 Feb 2018

My comp has been one of the 'lucky' ones with no real install or crash problems. Until now!!

On 17101 since the 15th but in the two nights previous to last night, the comp has crashed leaving a crash screen on the secondary monitor with the primary monitor black. (I leave my comp in sleep mode at night). The error was DRIVER POWER STATE FAILURE.

Then yesterday I came back to the comp to find coloured vertical lines all over my primary monitor. Switched monitor off and on and all was fine.

Got me thinking maybe it was the Intel HD Graphics display dvr that was giving these problems so I checked the Intel site and found a newer version was available so I installed that and my comp didn't crash last night. Clearly, too early to know whether it is fixed now but maybe others have had a similar experience??

For info, driver was ver 10.18.10.4358 dated 12-21-2015, or, for people like me, 21-12-2015! The new version was 4885, Nov 2017.

If it is now OK, interesting to know what changed in this w10 ver to cause the crashes.