Announcing Windows 10 Insider Fast+Skip Ahead Build 17035 for PC Insider

HippsieGypsie said:

Just got back from shopping. What the...hey. Still no AMD update yet?

I think they have permanently blocked AMD from getting the update. I can't believe its been over 2 days and still no build.

PLEASE NOTE: Due to a bug that causes PCs with AMD processors to bugcheck during upgrading to current builds, we are blocking PCs with AMD processors from receiving this build. We are investigating and working to fix so we can remove this block.

Why release it then?

Ask them.

martyfelker said:

PLEASE NOTE: Due to a bug that causes PCs with AMD processors to bugcheck during upgrading to current builds, we are blocking PCs with AMD processors from receiving this build. We are investigating and working to fix so we can remove this block.

Why release it then?

I totally agree—should not have been released.

magilla said:

I totally agree—should not have been released.

Yes it's a Fast Ring Insider build and bugs are to be expected but for MS to release a build with such a serious bug is totally unacceptable. Did they never think of testing it internally with AMD CPUs.
Shoddy debugging.

Scenario:. The team adds a feature to WinX that they want feedback on. Said feature breaks the OS on AMD CPUs.

Should they:

1) Spend resources fixing the issue for all users with AMD CPUs for a feature that might not make the final cut,

2) Release the build to users who can use it, and see if there is enough interest to pursue coding said fix above, or


3) Stop adding any new features, give you Fall Creators Update, say 'thank you for being an Insider but we no longer need your help'?

You be the judge.

The sense of entitlement that people have for a test build is plainly ridiculous

Fabler2 said:

Don't understand this attitude, as time after time on this forum we know that alpha previews will cause problems and in this case, at least, Microsoft identified that there was a problem with AMD processors and stopped a possible catastrophe to those users. You use pre-releases at your own risk anyway and still you complain if an AMD user?

Yes they identified there was a problem, but too late. Basic things like CPU compatibility of an OS should be tested even before an Alpha release.

DooGie said:

Yes they identified there was a problem, but too late. Basic things like CPU compatibility of an OS should be tested even before an Alpha release.

Happened a while ago with Intel graphics , a lot of feedback for it at the time, and took a long time to fix. The driver was Mobile Intel(R) 4 Series Express Chipset Family (Microsoft Corporation - WDDM 1.1) which was a CPU GPU chip. Might be a similar issue even if you have a dedicated card. I don't know, just guessing, but caused a lot of negative feedback at the time.