locked
Update to Windows 10 2004 blocked due to "generic hardware", setuperr and compdata info, "pc settings not supported" RRS feed

  • Question

  • Trying to upgrade a Windows 10 1909 to 2004.
    During the process, the update halts and this message is displayed: 

    Your PC settings aren't supported yet on this version of Windows 10. Microsoft is working to support your settings soon. No action is needed. Windows Update will offer this version of Windows 10 automatically when these settings are supported.

    When checking the compdata XML I can see the block is caused by a "generic hardware.":

    <HardwareItem HardwareType="Generic">
    <CompatibilityInfo BlockingType="Hard" Message="Your PC settings aren't supported yet on this version of Windows 10. Microsoft is working to support your settings soon. No action is needed. Windows Update will offer this version of Windows 10 automatically when these settings are supported." Title="This PC can't be upgraded to Windows 10."/>
    <Link Target="https://go.microsoft.com/fwlink/?LinkId=2133887" Value="Learn More"/>
    </HardwareItem>
    </Hardware>

    Setuperr:

    2020-06-28 14:51:12, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Suspend(1253): Result = 0xC1800104[gle=0x00000002]
    2020-06-28 14:51:12, Error                 MOUPG  CDlpTask::CheckUserInterruptEx(3060): Result = 0x800704D3
    2020-06-28 14:51:12, Error                 MOUPG  CDlpTask::CheckUserInterrupt(3112): Result = 0x800704D3
    2020-06-28 14:51:12, Error                 MOUPG  CSetupManager::ExecuteInstallMode(839): Result = 0x800705BB
    2020-06-28 14:51:12, Error                 MOUPG  CSetupManager::ExecuteDownlevelMode(409): Result = 0x800705BB
    2020-06-28 14:51:13, Error                 MOUPG  CSetupManager::Execute(294): Result = 0x800705BB
    2020-06-28 14:51:13, Error                 MOUPG  CSetupHost::Execute(433): Result = 0x800705BB
    2020-06-28 14:52:36, Error                 DU     DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057

    Troubleshooting steps so far:

    Commands:

    sfc /scannow

    Dism.exe /online /Cleanup-Image /StartComponentCleanup

    Dism.exe /Online /Cleanup-Image /RestoreHealth

    Disabled various Intel and MSI services, anti-cheat services (for gaming), in case they could be the reason for this situation.

    Antivirus is the Windows built-in.

    I know the message says "no action is needed", but I can't see how this can be fixed in the future if the issue is caused by a "generic" hardware that I don't know what is. The only generic hardware I can find in device manager, is the monitor with "Generic PnP Monitor" drivers. As far as I know, most monitors are using this generic driver. 

    Is there any way for me do actually identify what this "generic hardware" is? 

    Thank you.


    Kthxbai


    Sunday, June 28, 2020 12:59 PM

Answers

  • Hi, i have Got the same problem today and i was able to fix it. I have already my ISO 2004 and is the same problem. For sure is not the computer the problem I have a 8700k...

    So what I have did is to disable completely the internet on the computer, reboot the computer and install the iso and wait.. Work perfectly now you can reactivate the internet after.

    Is probably a bug on something when the installer verify the computer with internet before installing.




    • Edited by Maxime128 Sunday, June 28, 2020 5:17 PM
    • Marked as answer by Stoltenberg Sunday, June 28, 2020 10:58 PM
    Sunday, June 28, 2020 5:11 PM

All replies

  • I'm having this exact issues also. It's a new PC and 2004 upgrade checker clears, downloads and installs to 75% and hangs. sometime later a generic message "This pc can't be upgraded to windows 10. Your pc settings aren't supported yet on this version of windows"  
    Sunday, June 28, 2020 1:31 PM
  • Having the same issue. Needing to update so I can try out WSL 2.
    Sunday, June 28, 2020 3:28 PM
  • I am also having this issue.  I'm specifically trying windows 10 v2004 for WSL2/docker development. 

    Sunday, June 28, 2020 3:53 PM
  • Hi, i have Got the same problem today and i was able to fix it. I have already my ISO 2004 and is the same problem. For sure is not the computer the problem I have a 8700k...

    So what I have did is to disable completely the internet on the computer, reboot the computer and install the iso and wait.. Work perfectly now you can reactivate the internet after.

    Is probably a bug on something when the installer verify the computer with internet before installing.




    • Edited by Maxime128 Sunday, June 28, 2020 5:17 PM
    • Marked as answer by Stoltenberg Sunday, June 28, 2020 10:58 PM
    Sunday, June 28, 2020 5:11 PM
  • Thank you, Maxime!

    I can hardly believe it, but it seems to do the trick.

    I let the windows update assistant finish the download, and when it started updating, I unplugged the ethernet cable. Update completed, windows restarting to finish the update now.

    So I guess the updater does some kind of query in an online database right before it starts, and this responds with a "no go"..?


    Kthxbai

    Sunday, June 28, 2020 10:58 PM
  • Thank you, Maxime!

    I can hardly believe it, but it seems to do the trick.

    I let the windows update assistant finish the download, and when it started updating, I unplugged the ethernet cable. Update completed, windows restarting to finish the update now.

    So I guess the updater does some kind of query in an online database right before it starts, and this responds with a "no go"..?


    Kthxbai

    Is not the first time that windows does that to me for annual updates , i have trying many things the last time and i have found this way. When the installation will be finished, you can replug the cable and the monthly updates by windows update works well, everything work is not a problem.

    Exactly this is what i am thinking the updater make something on online and sometimes is bug.. I don't know why it still happens but at least my method works.

    The update 2004 is good and fast, no bugs so far.




    • Edited by Maxime128 Monday, June 29, 2020 12:01 AM
    Monday, June 29, 2020 12:00 AM
  • Thank you, Maxime!

    Your welcome I am happy for has able to help you. I have created a account here today with my email Microsoft only for helping you when I have see this thread by chance lol.

    Enjoy your windows 10.

    Monday, June 29, 2020 3:57 AM
  • Please provide feedback to Microsoft using the feedback hub:

    https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app

    Monday, June 29, 2020 4:21 AM
  • Same here. I'm needing up update for WSL 2
    Wednesday, July 1, 2020 8:46 PM
  • But the disconnect internet way doesn't work to me, maybe windows found that trick
    Thursday, July 2, 2020 5:53 AM
  • Wow, Thanks Maxime128 !
    I had the same problem and wasted hours on troubleshooting it..
    Your simple solution worked for me like a charm ! A+++++

    Thank u,

    Thursday, July 2, 2020 4:52 PM
  • I had the same error and it turned out I just needed to run a disk check on my c-drive. So after running "chkdsk /f c:" and rebooting, the next try was successful.
    Friday, July 3, 2020 11:06 AM