1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Don't install the Windows 10 Creators Update on your own, Microsoft advises

Discussion in 'Windows 10 Information and Alerts' started by starbuck, Apr 26, 2017.

  1. starbuck

    starbuck Rest In Peace Pete Administrator

    Joined:
    Sep 26, 2009
    Messages:
    3,830
    Location:
    Midlands, UK
    Operating System:
    Windows 10
    CPU:
    AMD Athlon II x2 250 Processor 3.00GHz
    Memory:
    8gb DDR3
    Hard Drive:
    500gb SATA
    Graphics Card:
    ASUS GeForce GTX 960 2gb
    Power Supply:
    650w PowerCool X-Viper
    Wait for Windows Update to ensure your hardware works properly, Microsoft says.

    0c4217ed5b62114bc60ab18b4bb2e9ab.jpg

    Microsoft would prefer it if you didn't try to install the Windows 10 Creators Update yourself.
    Instead, the company is encouraging everyone but advanced users to wait for the Creators Update to become available via Windows Update
    .

    That means workarounds for excited users, like the Media Creation Tool or the Windows Update Assistant, are discouraged.

    The reason for all this hesitation, according to Microsoft, is that the company wants to iron out any issues for specific hardware configurations before making the upgrade available to affected PCs via Windows Update. Microsoft is doing this using the feedback mechanisms in Windows Insider builds, as well as general feedback from users currently running the Creators Update.

    Microsoft says it usually takes one of three steps when there's a problematic issue in the Creators Update:
    • Document the issue and provide some troubleshooting advice on places like the company's forums.
    • Add a fix to Windows or work with a hardware maker to make a driver change.
    • Block impacted devices from receiving the Creators Update via Windows Update.
    .
    One issue that Microsoft cites as an example is a problem with certain Broadcom bluetooth radios that are having connectivity issues.
    Microsoft posted some troubleshooting advice on the company's forums once the issue was identified.
    The company also temporarily blocked anyone else with the same radio from getting the Creators Update over Windows Update.
    The company plans to remove the block once a solution is found.

    The story behind the story:
    Microsoft's old school software testing team was greatly reduced a few years ago, and it's pretty clear that the Windows Insider program isn't picking up the slack in full.
    So it's not surprising to see Microsoft encourage patience for those who want to upgrade.
    The Anniversary Update also had several issues in its early days, such as Kindle devices triggering the dreaded BSOD, broken webcams, and the infamous freezing issue.
    Annoying, undiscovered bugs are likely the new normal for the early days of Windows feature releases.
    As a result, most users should get used to waiting a little longer than expected for Microsoft's latest and greatest.


    Source:
    http://www.pcworld.com/article/3192...our-own-microsoft-advises.html#tk.rss_windows
     
  2. Mart

    Mart Registered Members

    Joined:
    Mar 7, 2017
    Messages:
    77
    Operating System:
    Windows 10
    I have just done a clean installation of the Creators Update on a recently bought second-hand laptop computer. It wasn't plain sailing but ended up working OK. The computer came with Windows 8.1 as the OS. It worked but I decided to see if it would upgrade to Windows 1o. The free upgrade period is over but I read that by downloading and using the Media Creation Tool (now the Creators Update version), the upgrade could still be done, so I went ahead and gave it a go.

    I decided to 'Keep nothing' when the option was offered during the upgrade procedure. The completed installation didn't need a key. Windows was already activated and everything worked OK.

    Looking at 'Disk Management' afterwards, there were still partitions present from the original manufacturer's Windows 8.1 installation, so the 'Keep nothing' option that arises during the procedure doesn't look to really mean that absolutely nothing is kept.

    Since those partitions were never going to be used and I now knew the OS would activate OK, I had another try in order to get the clean installation I wanted. All the partitions present on the disk were deleted this time (offered as an option during the W.10 installation procedure) before letting the new W.10 Creators Update files install.

    This was not so successful. Several things were wrong including the brightness and volume keys not working on the keyboard. Driver problems naturally. Windows had only given the keyboard a standard driver, not one designed to cope with those controls. I tried drivers from HP's site but nothing was successful. I updated the computer's BIOS and hard disk firmware while on the subject of updates but to no avail.

    The third and final attempt at a clean installation went very well. What made a difference to the previous attempts was allowing Microsoft full diagnostics access instead of the basic option. With this done, the keyboard was given the proper driver. The brightness and volume keys sprang into life when the installation was complete.

    I think this means it's best to give Microsoft full permissions on everything during a clean installation. Change those options after the installation has been completed if needs be. Just one driver that Windows couldn't provide was missing in Device Manager. Something to do with temperature control. Got this driver from HP and now all is well.
     

Share This Page