Parallels M1 Windows 10 Update 21382.1 Failed error Error 0xc1900101

Discussion in 'Windows Guest OS Discussion' started by JamesR40, May 14, 2021.

  1. JamesR40

    JamesR40 Bit Poster

    Messages:
    8
    Is anyone else seeing Error 0xc1900101 when they update Windows 10 to the latest preview build?

    Thanks!
    Jim
     
  2. ChristophS16

    ChristophS16 Bit Poster

    Messages:
    6
    Best Answer
    Go to the settings of the VM. Options > Sharing > Share Mac.
    Disable:
    • Share Mac user folders with Windows
    • Share iCloud, Dropbox, and Google Drive
    • Map Mac volumes to Windows
    Install the update and enable these options again.
     
    Maria@Parallels and GiuseppeP1 like this.
  3. SerMont

    SerMont Bit Poster

    Messages:
    32
    Yes, I have the same. It stopped installing on 20%
     
  4. MJHamilton

    MJHamilton Bit Poster

    Messages:
    16
    I see the same ... it also says that the current version has reached end of service a the top
     
  5. JesperL

    JesperL Bit Poster

    Messages:
    3
    I have the same problem, same error message, and installation fails at 20%.
     
  6. GiuseppeP1

    GiuseppeP1 Bit Poster

    Messages:
    1
    here the same.......
     
  7. ChristophS16

    ChristophS16 Bit Poster

    Messages:
    6
    Has anybody solved this issue?
     
  8. JamesR40

    JamesR40 Bit Poster

    Messages:
    8
    I tried creating a new VM from the image posted by Microsoft and got the same issue. I'll try again this morning.
     
  9. ChristophS16

    ChristophS16 Bit Poster

    Messages:
    6
    I failed also when trying to do the same.
     
  10. ChristophS16

    ChristophS16 Bit Poster

    Messages:
    6
    Temporarily disabling the sharing settings did the job for me.
     
  11. JamesR40

    JamesR40 Bit Poster

    Messages:
    8
    @ChristophS16 Can you be more specific on what you changed and where?
    Thanks!
    Jim
     
  12. JamesR40

    JamesR40 Bit Poster

    Messages:
    8
    @ChristophS16 Never mind, found it-- you need to disable Sharing at the Parallels VM level, not inside the Windows VM.
     
  13. ChristophS16

    ChristophS16 Bit Poster

    Messages:
    6
    Best Answer
    Go to the settings of the VM. Options > Sharing > Share Mac.
    Disable:
    • Share Mac user folders with Windows
    • Share iCloud, Dropbox, and Google Drive
    • Map Mac volumes to Windows
    Install the update and enable these options again.
     
    Maria@Parallels and GiuseppeP1 like this.
  14. MatthiasE5

    MatthiasE5 Bit Poster

    Messages:
    76
    I can confirm that, I researched various causes and figured it could be the plugged in usb card reade, or that .net was active as a windows feature, or that parallels was not isolated. It worked then. So it must have been the isolation, i.e. it suffice to go to security and simply enable isolation during installation.
    also the end of service note is nothing problematic, people are making fun of the phrasing.
     
  15. Maria@Parallels

    Maria@Parallels Kilo Poster

    Messages:
    8,694
    Hello guys,
    This issue is under investigation with Parallels Engineering Team and we are working on it.
    Could you collect the tech report once the issue reproduced and post the report's ID here please?
    This technical data will help us to find out the root cause of the issue and resolve it.
    Thank you in advance for cooperation.
     
  16. ChristophS16

    ChristophS16 Bit Poster

    Messages:
    6
    Does it make sense to submit the tech report after the update was installed successfully, or only if the issue is present?
     
  17. NoBackUp

    NoBackUp Bit Poster

    Messages:
    65
    Easy fix
    1) disable all sharing in Para Tools ... and I do mean all
    2) update to 21382
    3) reenable ...

    So not USB as reported here earlier as they completely changed USB Subsystem in 17

    already report also same issue in 17beta

    Worked for legacy VM (Full office etc installed) . been updating since first beta of 16 last year and also fresh install from 21345 Iso

    YMMV
     
  18. rahulk2

    rahulk2 Bit Poster

    Messages:
    1
    An error that begins with 0xC1900101 is usually a driver error. If you see any of these error codes, try the following steps first to fix the problem. If these steps don't work, see Resolve Windows 10 upgrade errors for more detailed technical info.
    • Make sure that your device has enough space.
    • Run Windows Update a few times.
    • Check third-party drivers and download any updates.
    • Unplug extra hardware.
    • Check Device Manager for errors.
    • Remove third-party security software.
    • Repair hard-drive errors.
     

Share This Page