• “please wait … system update” when booting Macrium rescue stick

    Home » Forums » AskWoody support » Windows » Windows 11 » Questions about Windows 11 » “please wait … system update” when booting Macrium rescue stick

    Author
    Topic
    #2427018

    “please wait while we install a system update”

    Had Macrium create the latest 8.0.6584 iso and created a flash drive with Rufus. when this failed I went to Mint and created it with usb image writer, but same result.

    It starts to boot with the square window image(winPE), then issues that message, looks like it’s trying to update the stick, and then powers down and restarts laptop. (Previous stick booted with slanted window image and booted fine.)

    So did Macrium somehow create a bad iso under windows 11? I suppose I could try under VM in Mint and see what it does.

    Thoughts? The updated Macrium was able to do a image under win10. Just this prob with the stick.

    EDIT: yeah… 🙁 I created that iso (same release) under WIN10 under VM under Mint (NOW you see why I have linux around! ) and it booted with the slanted window image and booted fine.

    So if I have Macrium create an iso under win11, it will think it is not updated and try to update the winPE. How useless is that?

    WIM for the one on win10 is RE 10 ver 2004, on win11 is RE 11 ver 22000.

    current update status:

    Screen-Shot-02-21-22-at-11.57-PM

    EDIT: I updated a couple of these but no change. I went to Macrium’s forum but didn’t see anything. I can’t post because I use free version.

    What am I missing?

    Viewing 9 reply threads
    Author
    Replies
    • #2427164

      Kris,

      I still use V6 but I let Reflect create the bootable disk directly. This has always worked perfectly for me. If this option is still in V8 I’d suggest you try it.

      May the Forces of good computing be with you!

      RG

      PowerShell & VBA Rule!
      Computer Specs

      1 user thanked author for this post.
      a
      • #2427237

        Thanks.

        Are you using win 11?

        I tried it and it kept telling me my 8gb stick was unusable because it was GPT even after formatting it with gparted, but it did write to a 32GB stick, but same result.

        No joy. even set bios to boot legacy first but same result.

    • #2427249

      Had Macrium create the latest 8.0.6584 iso and […] It starts to boot with the square window image(winPE), then issues that message, looks like it’s trying to update the stick, and then powers down and restarts laptop. (Previous stick booted with slanted window image and booted fine.)

      […]

      I created that iso (same release) under WIN10 […] and it booted with the slanted window image and booted fine.

      Given that evidence, my prime suspect would be the WinRE version being used. Under Win 11, perhaps you could try using an earlier RE version when building the iso. Select the Advanced option, “Choose Base WIM”, and select the Win 10 RE instead of Win 11. (I’m using MR 7, but I’m assuming the options are probably the same in MR 8.)

      If that works, that would point the finger at the Win 11 RE Macrium is using — either MS bungled the Win 11 RE such that it expects to be able to check for updates, or Macrium bungled the RE that it downloaded.

       

      1 user thanked author for this post.
      a
      • #2427261

        Correct. I created a winpe boot disk for AOMEI partition assistant and it did the same thing. So my winpe is bad. Apparently no on else’s is as google gets no hits. I posted to MS Q&A and left it there.

        Then I backed up my ssd and told Macrium to get win11 adk and it warned me it was getting a 1GB of stuff. Created the stick, booted fine, and took another backup. This way was probably much easier than stopping, getting the ADK, etc etc etc.

        Why am I the only one with a bad built-in winPE? Would it be corrected by a cold build of win11 (which I am far too lazy to do for only this issue, maybe later.)(this is an upgrade from 10 21H1 (or 21H2, I forget) )

        It IS easier to directly burn the stick and I will probably do it that way in the future.

        we’ll see if MS says anything on that forum…

    • #2427658

      However, just now I went to create a windows 11 recovery USB (system/recovery) it, after a very long time, produced a stick that boots with the OP message. iow, it creates  recovery stick with the default winPE. which is bad.

      Now how do I fix that????  This is now critical.

    • #2427674

      Did you try building it with Win RE, not PE, from the Advanced > Choose Base WIM screen?
      Which PE did you use, 5 or 10?

      cheers, Paul

      1 user thanked author for this post.
      a
    • #2427721

      Paul, there is no option to choose a wim on create a recovery drive.

      This pertains to the win11 operating system, not Macrium

      should I start a new post?

    • #2427730

      WinRE is the default on W10 and W11. If you can create a Macrium rescue image and that works it will show what is working and what is not.

      You can get a new WinRE by replacing the winre.wim file.
      See this thread: https://answers.microsoft.com/en-us/windows/forum/all/how-to-create-winrewim/93846771-0dda-4742-b563-48cda27885a1

      cheers, Paul

      1 user thanked author for this post.
      a
      • #2427752

        Paul, Thanks. C boot shows folders Macrium (macrium stuff,=), sm_da (alldb.db), and winpe_10_64 which shows the wimre.wim dated 5-21. I assume this is the wim I should replace?

        at MS I can dl the ADK or I can dl the ADK wim. Do I need to install the whole adk or can I just do the second install?

        Thanks

        EDIT. I installed adkwinpesetup.exe and went to C:Program Files (x86)Windows Kits10Assessment and Deployment KitWindows Preinstallation Environmentamd64en-us and copied winpe.wim to C:bootwinpe_10_64 and created rescue for AOMEI but still get same thing ask for update. What am I missing?

        Thanks!

        RE shows activeScreen-Shot-02-25-22-at-03.02-PM

         

    • #2427789

      This topic should be called bad winPE or bad wim.

      I am able to find nothing to guide me. so I wondered if programs that build winPE sticks are getting the wim from somewhere other than c:/boot . so I looked at my first SSD partition: it mentions boot and microsoft and recovery but no wim file.

      I looked at the first partition after my C:/ partition (win 11 recovery partition?) and it seemed to have the latest stuff as created by win 11 when I updated. Why isn’t it accessing it?

      I looked at the second partition after my C:/ partition and it seemed to be the recovery partition (old) for 10. The update to 11 did indeed create a new recovery partition when I did the update. This partition had older stuff and 2 recent special files (see a few paragraphs down). I decided to format this partition.

      win 11 still booted fine. The results of the adkwinpesetup.exe pgm also put 3 little execs into kitsScreen-Shot-02-25-22-at-05.42-PM
      So just for fun I click on each in turn. They only ran for 1 sec and no visible output, BUT, they did add those 2 special files to the initial drive fatScreen-Shot-02-25-22-at-05.45-PM
      (it’s the last 2 files.) I have no idea what they do. I have no idea what I am doing. I have no idea what to do. Latest test still tries to update when boot stick.
      Help please?

      Thanks!

    • #2427794

      and then I am searching all over to try to figure out how to boot win 11 into safe mode. F11 or F8 doesn’t work at initial startup. So I try holding shift while clicking restart in start menu.

      Guess what I got????? Please wait while we install a system update.

      HELP

    • #2427811

      this is way OT – started a new thread to try to resurect winPE

      https://www.askwoody.com/forums/topic/bad-winpe-wim-re-or-whatever-it-is/

      THANKS!

    • #2428005
    Viewing 9 reply threads
    Reply To: “please wait … system update” when booting Macrium rescue stick

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: