WIN10 1903 update fails - Your PC/Device needs to be repaired error code 0xc000000f

Discussion in 'Windows Guest OS Discussion' started by GrahamK1, Aug 22, 2019.

  1. GrahamK1

    GrahamK1 Bit Poster

    Messages:
    5
    I have just tried the WIN10 1903 update but after installation Windows reports "Your PC/Device needs to be repaired error code 0xc000000f" in a pale blue screen. The repair action checked the BOOTCAMP disk and found no errors. Other recommended key options did not work. This blue screen disappears after about 30 seconds. I managed to restore the previous version WIN10 1803 using a Winclone backup so I am running again but reluctant to keep fiddling with this upgrade so have deferred. I am running Parallels desktop V14 in MacOS Mojave on 2018 13" MacBook Pro. Has anyone had this experience? Any fixes out there? Should I perhaps run BOOTCAMP natively to perform the upgrade?
     
  2. Maria@Parallels

    Maria@Parallels Parallels Team

    Messages:
    3,696
    @GrahamK1 did you try to create new Bootcamp based VM?
     
  3. GrahamK1

    GrahamK1 Bit Poster

    Messages:
    5
    Maria, Thanks for your reply; no I didn't create a new BOOTCAMP based VM. Should I have done that? I have not had to do that before, after regular WIN10 updates or the 1803 feature update from 1709. I am not sure that I understand why that might solve the problem. It did occur to me that my problem might be a result of skipping the 1809 update which was initially reported as faulty - though I don't know why that should be the case.
     
  4. MattN

    MattN Bit Poster

    Messages:
    5
    I've had the issue issue (twice now) which is starting to get frustrating.
     
  5. Maria@Parallels

    Maria@Parallels Parallels Team

    Messages:
    3,696
    Guys, please collect the tech report right after the issue reproduced and post here the report's ID.
    Thanks in advance for your cooperation
     
  6. GrahamK1

    GrahamK1 Bit Poster

    Messages:
    5
    I have tried the upgrade again and report ID is 320663976. I will leave the system as is for 24 hours to see if there is any obvious resolution but then will need to revert to 1803. I attach the error screen shot. Thanks for looking at this.
     

    Attached Files:

  7. mmika

    mmika Kilo Poster

    Messages:
    326
    GrahamK1, do I understand correctly you tried to update Windows from within BootCamp VM?
    If so, you should not do so, because big feature update require EFI partition modification.
    You are at risk to break either Bootcamp VM or a native Bootcamp state.
    I would suggest to update windows from within native Bootcamp.
    After Windows updated via native Bootcamp you have to recreate Bootcamp VM to reflect changes in windows boot loader.
     
  8. GrahamK1

    GrahamK1 Bit Poster

    Messages:
    5
    Thanks for this advice - I tried native bootcamp (with version 1803 restored with Winclone) and now get message: "Inaccessible Boot Device". So I guess something is broken as you suggest. I can still use 1803 with Parallels. Any further suggestions please?
     
  9. mmika

    mmika Kilo Poster

    Messages:
    326
    I think you need to recover native bootcamp at first...
    If you have a lot of disk space (may be on external drives)
    you can "back up" you bootcamp by importing it to VM.
    This will make a copy of bootcamp as pure virtual VM (i.e. copy all windows data to image file in OS X).
    I suppose as you get BootCamp VM working this imported bootcamp VM will be working as well.
    After this you can try to recover native bootcamp, using Windows tools.
     
  10. GrahamK1

    GrahamK1 Bit Poster

    Messages:
    5
    Hi, did the report reveal anything helpful please? I have followed your earlier suggestion - deleted the existing BOOTCAMP VM and tried to create a new one (working with the WIN version updated to 1903) but the system just hangs (spinning dots under the window logo). I can also confirm that I consistently get this problem after the first reboot demanded by the upgrade process (blue screen says working on updates - do not turn off your computer - then attempts its first reboot). I also tried native BOOTCAMP having shut down Parallels and rebooted and get the same issue. So I have reverted again to 1803 version saved with WINCLONE - and reactivated Windows. I need to work with WIN10 so will wait to see if there are further ideas for resolution.
    To mmika: I have not tried your suggestion yet as I have WINCLONE backups so I am not sure why your suggestion would help. But thanks for the suggestion.
     

Share This Page