Dear Visitor,

Our system has found that you are using an ad-blocking browser add-on.

We just wanted to let you know that our site content is, of course, available to you absolutely free of charge.

Our ads are the only way we have to be able to bring you the latest high-quality content, which is written by professional journalists, with the help of editors, graphic designers, and our site production and I.T. staff, as well as many other talented people who work around the clock for this site.

So, we ask you to add this site to your Ad Blocker’s "white list" or to simply disable your Ad Blocker while visiting this site.

Continue on this site freely
  HOME     MENU     SEARCH     NEWSLETTER    
THE ENTERPRISE SECURITY SUPERSITE. UPDATED 13 MINUTES AGO.
You are here: Home / Windows Security / New Bug Hits Win 10 Creators Update
New Bug Hits Windows 10 Fall Creators Update
New Bug Hits Windows 10 Fall Creators Update
By Darren Allan Like this on Facebook Tweet this Link thison Linkedin Link this on Google Plus
PUBLISHED:
OCTOBER
26
2017
Another gremlin has been spotted in Windows 10's Fall Creators Update, with this particular issue reportedly causing installation to fail for those with certain motherboard and storage combinations.

The problem is said to primarily affect those who use a motherboard with Intel's X299 chipset and also have an NVMe SSD drive, as CNET reports (SATA solid-state drives are not running into trouble, apparently).

A similar bugbear hit home with the previous Creators Update back in the spring, as well, and now fresh folks are sitting through the same nightmare -- namely, when the PC reboots during installation of the upgrade, an error message is thrown up, and the install is simply failing.

The issue has affected those with Asus, MSI and Gigabyte motherboards, although CNET heard from one mobo vendor (the website didn't name which) that said it was unable to recreate this particular error.

So it's not clear if only a relatively small number of folks are affected here, but there are certainly a vocal group of error-message-sufferers across several support sites (including Microsoft's own answers forum, and the Asus ROG message board).

And they're not happy -- obviously enough -- particularly seeing as this error reportedly surfaced earlier this year.

The good news is Microsoft has said it's aware of the problem, and is currently working with manufacturers to resolve it. So for now, folks will have to sit tight.

Start Afresh

There is a confirmed workaround, although it's not exactly ideal: rather than update a current Windows 10 installation, you can perform a fresh install of the operating system from scratch, and in this case no problems are encountered.

But that's obviously considerably more hassle than performing a simple in-place upgrade.

Incidentally, if you need any sort of troubleshooting help with installing the Fall Creators Update, check out our guide on how to fix common problems with the upgrade.

Meanwhile, while the Fall Creators Update is still rolling out, Microsoft has deployed a new Redstone 4 preview build (the next big update due in 2018) for Windows Insiders (testers) in the fast ring.

This only consists of minor tweaks and bug fixes, mind, although it does rejig "ease of access" settings to better organize them, and introduces a new option for universal apps which run on startup that allows the user to view all tasks specified by the app developer. That's about your lot, though.

© 2017 T-break Tech under contract with NewsEdge/Acquire Media. All rights reserved.

Image credit: Microsoft.

Tell Us What You Think
Comment:

Name:

Like Us on FacebookFollow Us on Twitter
MORE IN WINDOWS SECURITY

NETWORK SECURITY SPOTLIGHT
China-based Vivo will be the first company to come out with a smartphone featuring an in-display sensor for fingerprint security, beating Apple, Samsung, and other device makers to the punch.

ENTERPRISE SECURITY TODAY
NEWSFACTOR NETWORK SITES
NEWSFACTOR SERVICES
© Copyright 2017 NewsFactor Network. All rights reserved. Member of Accuserve Ad Network.