none
Creators Update - Windows 10 is no longer supported on this pc. Uninstall this app

    Question

  • So now what?

    Cant go back.  Refresh shows the same cryptic message.

    The PC passed the requirements check at the start of the installation - 2 hours ago.

    Really Microsoft?  45 years in this game and this is the best you can come up with?

    Monday, May 08, 2017 4:06 PM

Answers

  • Microsoft Doesn't support the processor on your machine for the Creator Update.... Verified with Micro$oft.  They say its the vendor issue and vendor(s) say it's M$ issue, bummer!

    Devices that contain the following Intel processors (codenamed Clover Trail) are currently not supported on Windows 10 Creators Update:  
    Atom Z2760
    Atom Z2520
    Atom Z2560
    Atom Z2580
    Icons and text may not appear at all, or may appear as solid color blocks on devices containing these processors.  

    Microsoft is working with our partners to provide compatible drivers for these processors.  Until then, Windows Update will prevent devices containing one of the processors listed above from installing the Creators Update.  

    If your PC contains one of these processors, Microsoft recommends that you do not install the Creators Update from the software download site.  Please wait and allow Windows Update to install the Creators Update after compatible drivers are released and installed.  If you have already installed Creators Update from the software download site and are experiencing these problems, you can use Windows 10’s recovery options to go back to an earlier build.       

    There maybe some sort of better work-around for this, but I haven't found a great one yet.  I loaded windows on another machine with similar AHCI / UEFI BIOS, secure boot DISABLED, was able to use CloneZilla to make a copy of the working machine and restore it to the tablet that had issues with the upgrade, I force loaded the video driver and tablet is working.  I could never get it to "upgrade" to the Creator update, had to clone from another machine.  
    Wednesday, May 10, 2017 9:12 PM

All replies

  • Check Programs and Features in Control Panel and see whether you have any application with name "Windows 10" or similar?
    Monday, May 08, 2017 4:22 PM
  • Hi rod_bunny,

    What is the exact machine model? What is the present system version you are using? Is it available to uninstall that app manually?

    Try to restart the machine then check the symptom again.

    Try to update in a clean boot environment.
    How to perform a clean boot in Windows
    https://support.microsoft.com/en-sg/help/929135/how-to-perform-a-clean-boot-in-windows

    Best regards

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, May 09, 2017 7:11 AM
    Moderator
  • I don't have it in front of me atm but its an Asus VivoTab https://www.asus.com/us/Tablets/ASUS_VivoTab_Smart/

    Current build is 1607 14393.1066

    Restarted it and tried again, no difference.

    I'll try the cleanboot tonight.

    I'll also check for "Windows 10" to uninstall it.

    Update:

    There is no "Windows 10" apps

    Clean boot did not work.


    • Edited by rod_bunny Wednesday, May 10, 2017 4:33 AM
    Tuesday, May 09, 2017 8:18 AM
  • I, too, have this error.  As with the other user, I have no "Windows 10" app installed.  My machine is a Lenovo ThinkPad.  Very frustrating.
    Wednesday, May 10, 2017 1:05 AM
  • Microsoft Doesn't support the processor on your machine for the Creator Update.... Verified with Micro$oft.  They say its the vendor issue and vendor(s) say it's M$ issue, bummer!

    Devices that contain the following Intel processors (codenamed Clover Trail) are currently not supported on Windows 10 Creators Update:  
    Atom Z2760
    Atom Z2520
    Atom Z2560
    Atom Z2580
    Icons and text may not appear at all, or may appear as solid color blocks on devices containing these processors.  

    Microsoft is working with our partners to provide compatible drivers for these processors.  Until then, Windows Update will prevent devices containing one of the processors listed above from installing the Creators Update.  

    If your PC contains one of these processors, Microsoft recommends that you do not install the Creators Update from the software download site.  Please wait and allow Windows Update to install the Creators Update after compatible drivers are released and installed.  If you have already installed Creators Update from the software download site and are experiencing these problems, you can use Windows 10’s recovery options to go back to an earlier build.       

    There maybe some sort of better work-around for this, but I haven't found a great one yet.  I loaded windows on another machine with similar AHCI / UEFI BIOS, secure boot DISABLED, was able to use CloneZilla to make a copy of the working machine and restore it to the tablet that had issues with the upgrade, I force loaded the video driver and tablet is working.  I could never get it to "upgrade" to the Creator update, had to clone from another machine.  
    Wednesday, May 10, 2017 9:12 PM
  • Thanks... it is an Atom processor (1607 14393.1066 shows it as such) 

    So that's 3 of my PCs not getting an upgrade... (not that 2 of them ever left 7 Pro)

    The weird thing is that it passes the Processor check at the beginning of the update process ie just before it asks to confirm start of the upgrade. That error comes up near the end.

    Its a bit late to do a compatible Processor check at the end of the upgrade..... cart before the horse?

    So what's the plan MS?  Now that you are orphaning processors from the one current build philosophy.  Are we going to see a fragmentation ala android in the future?


    • Edited by rod_bunny Thursday, May 11, 2017 6:30 AM
    Thursday, May 11, 2017 6:26 AM
  • Really? cound not check that first ? and why doesnt say processor not supported ? so amateur.... and worse, the creator suggestion came from Windows update. Microsoft has zero respect. At least thanks for the answer.

    Wednesday, June 28, 2017 8:07 AM
  • same problem here with a Acer tablet w510. 

    Why does MS install the win10 update software on my system when they already know it wont work.

    I am really angry! 

    Saturday, July 08, 2017 6:17 PM
  • I have an HP Elitepad 900 tablet with an Atom Z2760.  I used this as my Windows Insider machine on the Fast Ring and updated to Creators update 1703 without problem. As per MS recommendations, I switched to the Slow Ring and, when trying to update the first slow ring release since 1703, I get the same message.  So, 1703 supported, at least on my tablet but subsequent builds not supported?

    Regards,

    Sunday, July 09, 2017 12:41 AM
  • Sorry to say that, but the very same problem already came up with the upgrade from WIN8 to WIN10. This is how I solved it last time. This will surely work again: 

    I created an image of the new Windows installation file. I installed it from a USB device on the tablet (acer iconia w510). Then, I installed an old graphics driver for WIN 8. And guess what happens?! Yes, it works perfect. No graphic problems. No icons appearing as a block. No elements disappearing at all. Just perfect performance.

    What I really wonder about is: Why does MS not publish this workaround? Why are the graphic drivers in the Windows updates not left as they are, but changed to versions which do not suppport the devices of thousands of users? 

    Have a nice day all of you. 

    Friday, July 21, 2017 6:19 AM
  • I don't blame you. They did the same to me.

    One tech rep asked if I had installed the original Windows 10 update by myself.  When I told him I did, he tried to distance MS from the problem by saying I should gotten permission from them first.  He backed off of that real quick after I told him to point out where in my EULA does it say I need to get MS permission before installing a mandatory update.  (I even got him to admit the "N"-word on their part... "negligence")

    Hasn't helped though.  They still washed their hands of the matter, even though they know they messed up, and that they could have avoided it by just spending a little extra time training their tech personnel better.

    Sad.
    9 hours 37 minutes ago