Forum Discussion

Dollza's avatar
Dollza
Brass Contributor
May 01, 2022
Solved

Can't install windows 11 Insider Preview 22610.1

I'm on build 22593. I couldn't upgrade to build 10.0.22598.100 (error 0x80070002) later I couldn't upgrade to build 10.0.22598.200 (same error 0x80070002)

I tried to stop and delete services in the softwaredistribution folder (did not help). And I tried sfc /scannow. Windows says all files are intact. And did dism /online /cleanup-image /restorehealth. And I still can't install. There is an installation of 23% and later the computer reboots and writes "the change is being rolled back." I also read virtualization, you need to enable it, but I also have it enabled. Someone can help?

  • Dear people. Thank you for trying to help me, thank you very much. I solved the problem quite simply, I decided to reset the system to factory settings. And yes, I successfully managed to update after that. Thanks again to everyone who tried to help.

47 Replies

  • Garrie_Bennett's avatar
    Garrie_Bennett
    Copper Contributor

    I can update no problems at all as long as I do not got the delta version of Insider.

    When I go to the latest upgrade on delta i get "Windows 11 Insider Preview 22621.1      8% download and it stops. Then I get a fault that reads "We couldn't update the system reserved partition"

    • Dollza's avatar
      Dollza
      Brass Contributor
      Have you tried to fix the problem in my way that I wrote earlier?
  • Dollza's avatar
    Dollza
    Brass Contributor
    Dear people. Thank you for trying to help me, thank you very much. I solved the problem quite simply, I decided to reset the system to factory settings. And yes, I successfully managed to update after that. Thanks again to everyone who tried to help.
  • Callistemon's avatar
    Callistemon
    Copper Contributor
    The Behavior:Win32/Powessere.SA and 0xc190011f error was a result of using Skip_TPM_Check_on_Dynamic_Update for bypassing the Despicable Requirements of Windows 11. After that CMD was run again to uninstall, no threats were blocked while updating, instead a Setup window appeared to complain about the Despicable Requirements, then a different error code occurred after that's closed. Only build 22610 had this issue. Once 22616 was available, having Skip_TPM_Check_on_Dynamic_Update made the Setup window open instead of being blocked, which then proceeded through without the Despicable Requirements.
    • Dollza's avatar
      Dollza
      Brass Contributor
      I didn't understand why it was addressed to me? I do not have such an error, and I repeat 3 times that I have tpm to change (it is enabled). The hardware is compatible with a Windows 11 installation.
      • Callistemon's avatar
        Callistemon
        Copper Contributor
        I was too dumb to find how to add another comment to the post without replying, but I should have chosen the closest relevant one instead of the original post.
    • Aaron_Liu's avatar
      Aaron_Liu
      Copper Contributor
      I've also filed a report: https://aka.ms/AAgv4xj
      Like I said, usually the error happens due to a false positive with windows security, causing the "driver error" that was actually windows security's live protection.
      • KevinKraze's avatar
        KevinKraze
        Copper Contributor
        I was able to update to the new build, 22616, succesfully.
    • Dollza's avatar
      Dollza
      Brass Contributor
      Alas, this is not my problem. I have tpm.
    • KevinKraze's avatar
      KevinKraze
      Copper Contributor

      Aaron_Liu My computer however, is fully supported by windows 11. So it can't be that (at least for me)...

  • KevinKraze's avatar
    KevinKraze
    Copper Contributor

    Dollza I am also getting this issue with the same build. After trying to upgrade with the ISO (which failed) I checked the logs and this error stood out to me:

    DRVMIG: Failed to inject driver package in the new OS: C:\Windows\System32\DriverStore\FileRepository\cdc-acm.inf_amd64_53a164dc20d3fb67\cdc-acm.inf. Error: 0x80070002[gle=0x0000007a]

    Seems the starting with build 22598, some driver incompatibilites started. We might just need to have to wait for a new build to come out with fixes.

    • Dollza's avatar
      Dollza
      Brass Contributor
      So how long to wait? Update 2 has already been released and there is no result.
      • shenlong2210's avatar
        shenlong2210
        Copper Contributor
        My PC is i5 4590 32GB RAM with AMD Vega64 NOT enough requirement to install Windows 11 so I need a treat modify installation at begining
        So I think when we update new release, they may be encounter a bug. If you meet warning virus, just Disable Security; if yuu meet BSOD just plug neccessary devices, remove other hardware and make sure storage is enough 20GB minimum.
  • fedrob's avatar
    fedrob
    Copper Contributor

    DollzaI get error 0xc190011f but also I get a security msg saying threat detected when I start the update - Behavior:Win32/Powessere.SA 

    weird

    • shenlong2210's avatar
      shenlong2210
      Copper Contributor

      fedrob Yes, you're right.

      My PC show security message so I disabled Windows Secirity by turn off services.

      Then I update Windows success.

      • Dollza's avatar
        Dollza
        Brass Contributor
        Can you tell me in more detail what services you turned off and what settings in Windows security
  • SeanRosenberg's avatar
    SeanRosenberg
    Copper Contributor
    I have the exact same problem and have tried everything on Google, still didn't work.

Resources