Seems like this Creator update may take its time per MS, its OK for most people, as not everybody feels like messing around with it anyway as long as their machine "works" why bother. So I assume it will show up sooner or later. I'm not gona bother with it myself again either. Its installed and running fine on my old desktop, my laptop is the one that gave me that stupid bug, it ran OK, but I don't like it when I can't find my own solutions to fix stupid annoying bugs.
Here's MS's take.
====================
Two weeks ago, we began rolling out the Windows 10 Creators Update. Today, I’d like to share some insights into the feedback we’re hearing, and some specific ways we plan to use that feedback to adjust our rollout process.
As we
previously announced, the first phase of the rollout targets newer devices. Based on testing work done with our OEM hardware and ISV app partners, we believe these devices will have the best possible update experience and help us decide when it’s time to begin the next phase of the rollout.
The millions of customers now running the Creators Update have provided us valuable feedback on the update experience as well as the product itself. We’re also seeing many customers use the
Feedback Hub app to search for issues they are having and “upvote” the issue, which in turn helps us quickly spot issues others may be experiencing. By choosing to enable the diagnostic settings at the “full” level in your
privacy settings, the Feedback Hub app is also able to provide the associated diagnostic data based on the specific issue you are reporting – this data helps us diagnose and address issues faster.
While it is fantastic to see all the positive feedback on the new features and update experience in the Creators Update, we actually focus more on the issues users are reporting so we can improve the overall experience over time. Depending on the individual issue, we do one or more of the following:
- Document the issue and provide users more information on the issue, potential user impact, and (in some cases) specific guidance including troubleshooting or workaround/remediation guidance. You can find more information via our support channels, including the Windows community forum.
- Update Windows itself, or work with a PC, accessory, or ISV app partner to post a driver or compatibility update.
- Deploy a “block” to prevent further rollout of the Creators Update to impacted devices until an issue is resolved.
Blocking availability of the update to devices we know will experience issues is a key aspect of our controlled rollout approach. We decide what to block based on user impact, and blocking issues are a high priority for us to address as quickly as possible. During the time it takes to address an issue, we want to limit the number of customers exposed to that issue. For example, our feedback process identified a Bluetooth accessory connectivity issue with PCs that use a specific series of Broadcom radios, ultimately resulting in devices not reconnecting as expected. Once identified,
we posted this issue to our Windows community forum, provided user guidance on troubleshooting, and blocked additional devices with these specific Bluetooth radios from updating. Once a solution is available, we will update our forum post and remove the block.
It’s important to note that when customers use the
Software Download Site to manually install the Creators Update they bypass many of these blocks. Therefore, we continue to 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. When your device becomes eligible for the Creators Update rollout, you’ll be prompted to make some important choices on your privacy settings before the Creators Update can install.
Please continue to give us feedback about your experience via the
Feedback Hub app. We hope you enjoy the Creators Update, and I’ll be providing more updates on the rollout soon.
