Creators Edition Bugs

[RLGL]

Stumbled across the following:

Technology
Windows 10 Creators Update may have bugs - do not install it manually, warns Microsoft

Agamoni Ghosh,International Business Times 3 hours ago

• Reactions
  
• Sign in to like
  
• Reblog on Tumblr
  
• Share
  
• Tweet
  
• Email

Microsoft has warned Windows 10 users to not install the latest creators update manually as it may contain bugs. The company says users should wait for an automatic update to become available in their region.

The company further explains that the latest update will roll out slowly because it has come across errors that may cause problems for non- tech savvy users. Microsoft said that it has blocked the availability of the update to devices that it knows will experience the issues.

Trending: FalseGuide botnet malware infects 2 million Android phones

"When customers use the Software Download Site to manually install the Creators Update they bypass many blocks. Therefore, we recommend (unless you're an advanced user who is prepared to work through some issues) that you wait until the Windows 10 Creators Update is automatically offered to you," the company said in its blog post.

Users, who have been trying to install the creators update, have complained about several problems including installation errors, missing features and connection issues with accessories like Bluetooth speakers and mouse.

Don't miss: New Samsung app hits the brakes on texting while driving

The company says it wants to make sure it fixes all errors including patches for different hardware configurations before making the upgrade available to all. Microsoft has a feedback mechanism in Windows Insider that allows users to directly let the company know about any issues with the software.

In case you have already installed the update manually and are facing issues, you can roll back to the older version of Windows 10. Check out our tutorial and follow the steps to downgrade from the creators update.

 

[MustISO]

Impossible, Microsoft has an impeccable record for quality releases.

 

[RLGL]

Impossible, Microsoft has an impeccable record for quality releases.

ROFL

 

[woozle64]

I guess I've been lucky, I've had very little issues on my Ryzen build with a W10 creator install.

I did have many issues trying to use an old W10pro disc on the same Ryzen PC...in my great wisdom, I didn't see a problem using a 2015 windows build on the new Ryzen arch. I had the joy of experiencing 30+ lockups/bsods in a single day

 

[BonzaiDuck]

I guess I've been lucky, I've had very little issues on my Ryzen build with a W10 creator install.

I did have many issues trying to use an old W10pro disc on the same Ryzen PC...in my great wisdom, I didn't see a problem using a 2015 windows build on the new Ryzen arch. I had the joy of experiencing 30+ lockups/bsods in a single day

No, that makes sense. MS knew Ryzen was being released. That being said, they may not have had a clear anticipation when they released the earliest or even Anniversary builds. So you would have to have resorted to the IT-Administrator's or Full Download.

I can report that there has been a set of symptoms common to systems using NVMe SSDs and caching software. The range of users who completely resolved those problems, that I know of firsthand, seems to be 1 out of 3, and if a second person obtained partial resolution, I'm the one with the most robust result.

But my experience with the direct-download Full version was troubled, either because it was my first pass and experience -- not knowing what to expect -- or because there are, as MS says, a spate of bugs or problems with that approach. My second pass began with getting it through Windows Update, or at least through the web-site that links from WU, and thank god I saved it in my browser history. Once I went there and chose to back out, WU stalls at updating the very thing the link would otherwise have given: the WU Assistant. So this seems to validate the MS advice.

Even after that, I still had symptoms pertaining to the boot drive and my dual-boot configuration. The Win7/Win10 boot-menu didn't function properly in a lopsided way, even though both OSes were accessible. I uninstalled and reinstalled my Samsung 960 Pro/EVO drivers and Magician 5, which seemed to eliminate the message at boot-time "Diagnosing/Scanning/Repairing . . . {GUID} Volume . . "

I just made it difficult for myself for having installed Windows 7 on this system first, as opposed to a Win 10 install followed by Win 7 (which seems counterintuitive, anyway). I think I tweaked it to the perfection that nobody here expected. I was being gently prodded to "start fresh." Instead, this is an evolution of tweaks and software installations since early October.

As much as I can see, I'm good to go. But the problems, software glitches and hardware choices I've seen associated with them are confirmed, as is the MS direction to "go through Update."

 

[sm625]

Stumbled across the following:

Technology
Windows 10 Creators Update may have bugs, do not install

Article should just end right there. "Bugs" are little things like a window always opening partially off the screen. But when an update totally destroys your network connection, that isnt a bug, that is a disaster that should put a company out of business.

 

[BonzaiDuck]

Article should just end right there. "Bugs" are little things like a window always opening partially off the screen. But when an update totally destroys your network connection, that isnt a bug, that is a disaster that should put a company out of business.

The logic of it causes me concern. Like I've said many times, I went through a week's-worth of hell over Build 1703. I haven't found a single flaw, although I suspect the possibility of one, after my discovery in the thread posted over at "CPUs and OC'ing." But my discovery is consistent between 1607 and 1703 . . . .

I can't confirm the behavior I may have mentioned earlier for other folks, but you can be "tricked" into going forward with it, if you follow the link from the Windows Update screen announcing the new build. If I backed out of it after a brief "investigation," it borked my Update into a continuous "0% completed" for installing KB . . . 240.