Failed To Install Windows 10 Version 1703
How to upgrade an old PC to Windows 10 - free Microsoft's much-hyped free upgrade offer for Windows 10 ended last year, right? Here's how to get yours.Video: How to upgrade an old PC to Windows 10 - freeUpdate 19-July-2017: Microsoft has acknowledged this issue and has agreed to extend the support deadline, delivering security updates for affected devices until 2023. For details, see. Several portions of this post have been updated to reflect that statementSome PCs that received a free upgrade to Windows 10 less than two years ago are now officially blocked from receiving future updates. Windows 10.If you are one of the unlucky owners of one of the first 2-in-1 PCs, announced in 2012 and sold throughout 2013 and 2014, your PC was eligible for the free Windows 10 upgrade in mid-2015, and it also received the Summer 2016 Anniversary Update (version 1607) without any compatibility issues.But when Windows Update tries to install the March 2017 Creators Update, version 1703, the installation fails with a dire (and confusing) message that reads:Windows 10 is no longer supported on this PCUninstall this app now because it isn't compatible with Windows 10. I was able to confirm that this hard block exists by attempting to install the Creators Update on an HP Envy X2, which uses a Clover Trail CPU, the Atom Z2760. HP shipped me the device in early 2015 and I've used it in lab tests as a benchmark for low-spec CPUs.The compatibility check that's part of the Windows Setup program gave this system a clean bill of health, but after downloading more than 3GB of setup files for the Creators Update, the upgrade failed, with the error message shown above.There's no way to work around the block, either.
Without a fix for the underlying compatibility issue, this device is stuck on Windows 10, version 1607.And that's a big problem for owners of those devices., Microsoft's servicing policy says, 'Each Windows 10 feature update will be serviced with quality updates security and reliability fixes for 18 months from the date of the feature update release.' If Microsoft sticks to its announced support deadlines, any device running Windows 10 version 1607 will stop receiving updates in early 2018. In some cases, this cutoff date will be only three years after those devices were placed in service.
Update: Microsoft now says it will extend the deadline for those devices, allowing them to continue receiving security and reliability updates until 2023.A search of Microsoft's website doesn't turn up any support documents that explain this serious compatibility issue. I did find confirmation from Acer, which published this support note: The following Intel Clover Trail processors are currently not supported on Windows 10 Creators Update:. Atom Z2760.
Atom Z2520. Atom Z2560. Atom Z2580Microsoft is working with us to help provide compatible drivers to address this incompatibility.
If you install the Windows 10 creators update, icons and text may not appear at all, or may show up as solid color blocks or bars. If you have already installed Creators Update and are experiencing problems, you can use Windows 10 recovery options to restore your system to the previous build.That note is echoed in a reply in. That thread was marked as an official answer by forum moderators, including one identified as 'Microsoft contingent staff.' When you try to upgrade a Clover Trail-based PC to the Creators Update, Setup returns the error code 0xC1900209, which 'the system does not pass the compatibility scan to install the update. Incompatible software is blocking the upgrade process.'
The entire affair brings back memories of a confusing announcement in the months before the launch of Windows 10.In January 2015, Windows boss Terry Myerson using this language. I've highlighted the head-scratching caveat that was included: This is more than a one-time upgrade: once a Windows device is upgraded to Windows 10, we will continue to keep it current for the supported lifetime of the device - at no additional charge.
emphasis addedThat odd phrase confused a lot of people and launched more than a few conspiracy theories. In July 2015, two weeks before the official Windows 10 launch date, Microsoft and clarified the 'supported lifetime of the device' policy with this footnote. Here, too, I've highlighted the relevant portion:. Updates are cumulative, with each update built upon all of the updates that preceded it.
Failed To Install Windows 10 Version 1703 Version
A device needs to install the latest update to remain supported. Updates may include new features, fixes (security and/or non-security), or a combination of both. Not all features in an update will work on all devices. A device may not be able to receive updates if the device hardware is incompatible, lacking current drivers, or otherwise outside of the Original Equipment Manufacturer's ('OEM') support period.
Update availability may vary, for example by country, region, network connectivity, mobile operator (e.g., for cellular-capable devices), or hardware capabilities (including, e.g., free disk space). emphasis added. Where do you draw the line on personal privacy?
The right options are different for everyone.This is the first example of hardware that was initially supported by Windows 10 but has since run afoul of those rules.Microsoft and its OEM partners made a big deal of this entry-level Atom processor for the first wave of Windows 8 devices. An from the launch event in September 2012 highlighted eight tablets and hybrids from Acer, ASUS, Dell, Fujitsu, HP, Lenovo, Samsung, and ZTE.The devices themselves were because of driver problems.The HP Envy X2 was a relative star among this class of PCs, boasting a real-world battery life measured in days, with a detachable tablet that compared favorably in size and weight (but not app support) to the then-current iPad model. (You can read my first impressions of the device in the March 2013 post, )Some three- and four-year-old PCs are unable to install the latest Windows 10 updateThe Envy X2 went on sale at a starting price of $849, but the price was cut by $100 shortly thereafter.
HP and its distributors continued to offer the device until its replacement arrived some two years later, and bargain hunters could still find it for sale in 2015.No one knows exactly how many Clover Trail-based devices were sold, but collectively the total from all manufacturers was probably in the millions. Analyst Ben Bajarin, who tracks PC and tablet sales closely, estimates that the total number of Clover Trail devices sold was over 10 million. Today, owners of those devices who took advantage of Microsoft's free upgrade offer for Windows 10 are facing a rude shock.Acer's support note implied that Microsoft and Intel were working together to release a software fix for this issue, but Microsoft's statement of July 19 confirms no such fix is coming.Are there other PC architectures that are likely to face this issue in the next year or two? We don't know. As Microsoft moves to a Windows 10 upgrade cadence of twice a year, with feature updates delivered in March and September and a support lifecycle of 18 months, that support policy can in theory cause even a two-year-old device to end up on the Island of Lost CPUs.The irony in this case is that Microsoft aggressively pushed the free Windows 10 upgrade offer to the owners of these devices, as the July 2016 cutoff date approached. Now, less than a year later, those devices are being cut off without notice.The bottom line: If your PC was originally designed for Windows 8 or Windows 8.1 and the manufacturer doesn't officially support it for Windows 10, you're at risk.For the short term, at least, this policy shouldn't affect PCs that were designed for Windows 10 or for which the manufacturer has explicitly delivered support for Windows 10 in the form of drivers and firmware updates.
But that could change in a few years, perhaps without notice. Related Topics. By registering you become a member of the CBS Interactive family of sites and you have read and agree to the,. You agree to receive updates, alerts and promotions from CBS and that CBS may share information about you with our marketing partners so that they may contact you by email or otherwise about their products or services.You will also receive a complimentary subscription to the ZDNet's Tech Update Today and ZDNet Announcement newsletters.
You may unsubscribe from these newsletters at any time.ACCEPT & CLOSE.
Microsoft released KB4032188 today, a new cumulative update for Windows 10 Version 1703, the Creators Update version of the Windows 10 operating system.The cumulative update is already distributed through Windows Update, and also as a standalone download at the Microsoft Update Catalog website.The update brings the version of the operating system to build 15053.502. It features no new features - no surprises there as the release of the Fall Creators Update for Windows 10 is just around the corner. Windows 10 Version 1703 KB4032188The release fixes many issues that Windows 10 version 1703 users may have run into. Microsoft did patch major issues in this release, for instance one issue where device drivers were not loading, a stability issue of USB host controllers that would no longer respond to attached peripherals, a MP4 video playback issue in Edge, and a memory leak on network bridge setups.The full list of changes is attached below. You find information on the Microsoft Support website. Addressed issue that causes a Microsoft Installer (MSI) application to fail for standard (non-admin) users when installed on a per user basis. Addressed issue to enable support in the DevDetail Configuration Service Provider (CSP) to return the UBR number in the D part of the SwV node.
Addressed issue where NTFS sparse files were unexpectedly truncated (NTFS sparse files are used by Data Deduplication—deduplicated files may be unexpectedly corrupted as a result). I too have experienced Windows 10 upgrades that have either stalled at X% or have failed to recognize a device (most notably, my graphics adapter) after installation. Black screen, followed by a forced version downgrade.
Hours wasted.I know these problems are widespread. They’re reported on various user forums all over the internet. Even worse – upgrades are pushed to users – who have to jump through hoops to learn how to disable or block them.Something is flawed in Microsoft’s approach. Users shouldn’t be playing Russian Roulette on every Windows OS upgrade. Meanwhile, I have been running Win 7 “LTSB” and Linux Mint 17.3 LTS(EOL in 2019) stably since 2011 and 2016 respectively.Except for the Ent LTSB edition, Win 10 will always be Beta software, like the unstable Linux Rolling Releases.M$ will do anything for more profit$, hence their twice-yearly unstable upgrades for Win 10 = EOL of 18 months for each new Version.
Some corporations buy or will buy Win 10 Ent E3 Volume Licenses and they have to or will have to pay for the upgrades, ie by additionally buying the costly Software Assurance/Insurance = forced to lease or subscibe. Even the greedy Apple only dish out yearly upgrades for iOS and MacOS.
Hi there, my merc stealth is broken too. It is recognized and works as a “normal” keyboard, but I can’t use any of its features (macros, mods, key reasignation)I’m pretty sure that the guilty is the KB4034674 update (a small one after to the “big” creators update). Restoring the pc to a point before this update fixes the problem, even having creators update working. It’s KB4034674. 99,9999% sure.For now, my temporary solution is restore the pc to a pre-upgrade point and block the updates (I can do this just for 30 days with win10 PRO), waiting for a solution.Is there anyway to block just this update permanently? What is that “wushowhide.diagcab” tool that you have mentioned above?Regards.