Unable to Safe Mode in order to troubleshoot Windows Update issue

Page 3 of 3 FirstFirst 123

  1. Posts : 42,922
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #21

    The 100Mb partition is the EFI partition. You're missing the 16Mb partition - or it's not shown by the program you're using.

    Compare my screenshot, and note how using Minitool Partition Wizard how the partitions are helpfully described.

    NavyLCDR is a person. A member.

    You are referring to the wrong link: rebuild - see link in
    Unable to Safe Mode in order to troubleshoot Windows Update issue - post #15
      My Computers


  2. Posts : 89
    Win 10
    Thread Starter
       #22

    dalchina said:
    The 100Mb partition is the EFI partition. You're missing the 16Mb partition.

    NavyLCDR is a person. A member.
    Well I'll try to rebuild it then. No problems booting up the computer (except in safe mode).

    I understand that NavyLCDR is a person. I don't understand what "wait for" is meant to mean.

    Does this person usually drop in and respond to these threads?

    BTW, thank you for your time up to this point. It is really appreciated even if I'm stuck in the mud.
      My Computer


  3. Posts : 42,922
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #23

    By 'mentioning' a member with the '@' that member receives a notification.
    Should that member then choose to look at the thread mentioned and choose to respond, you should see that response.

    You are making progress- we know the problems, and you have the means to
    a. rebuild the 16Mb MSR partition
    b. recreate a valid Recovery partition
      My Computers


  4. Posts : 89
    Win 10
    Thread Starter
       #24

    dalchina said:
    By 'mentioning' a member with the '@' that member receives a notification.
    Should that member then choose to look at the thread mentioned and choose to respond, you should see that reponse.
    Ah, okay. That's pretty cool. Here's to hoping!

    Thank you.
      My Computer


  5. Posts : 42,922
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #25

    If you still can't copy the file you can do it
    - by booting your PC from a live boot disk (Google/ search if you don't know what one is).
    - by booting to a command prompt and then copying (a bit tricky getting partition drive letters right plus navigating).
    - using a free utility like Emco MoveonBoot
    Download EMCO MoveOnBoot - MajorGeeks
    - which does the copying on restart if necessary

    All the above avoid permission restrictions as Windows is not running.
      My Computers


  6. Posts : 89
    Win 10
    Thread Starter
       #26

    dalchina said:
    If you still can't copy the file you can do it
    - by booting your PC from a live boot disk (Google/ search if you don't know what one is).
    - by booting to a command prompt and then copying (a bit tricky getting partition drive letters right plus navigating).
    - using a free utility like Emco MoveonBoot
    Download EMCO MoveOnBoot - MajorGeeks
    - which does the copying on restart if necessary

    All the above avoid permission restrictions as Windows is not running.
    I mentioned earlier that I did copy the file over successfully.

    After doing the "reagentc" thing, the file is no longer visible and in its place is ReAgent.xml.

    But it still gives an error.

    I just finished creating a fresh Windows 10 install USB (my original no longer registers when plugged in).

    Trying to get the system to boot into it. If it isn't one thing...
      My Computer


  7. Posts : 42,922
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #27

    Assuming you got the same error message when using reagentc as you posted 1st, see:

    reagentc /enable failing with error code 3bc3, Windows Update failing with error 800F0922 - Super User

    I'm guessing you somehow tried to move your O/S to a new disk (you mentioned a larger disk), but only copied certain partitions and somehow this led to this mess. There are decent ways to clone disks.
      My Computers


  8. Posts : 89
    Win 10
    Thread Starter
       #28

    dalchina said:
    Assuming you got the same error message when using reagentc as you posted 1st, see:

    reagentc /enable failing with error code 3bc3, Windows Update failing with error 800F0922 - Super User

    I'm guessing you somehow tried to move your O/S to a new disk (you mentioned a larger disk), but only copied certain partitions and somehow this led to this mess. There are decent ways to clone disks.
    Thank you.

    I did a CLONE drive following instructions from the Partition Master site.

    I bumped up a couple of drives from 500g to 1tb leaving me with 3 - 1tb drives and an original 500gb drive (so 4 SSD drives). When I built the machine and purchased Aorus X570mb, took advantage of the special SSD slots.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:01.
Find Us




Windows 10 Forums