WINPE rescue media

I believe what happened is that the WinPE system you booted to is set up to the default time zone of GMT-8. Since you are in GMT+1, you see a nine hour (not 10) difference in how the time is displayed when you boot to Windows.

J'ai suivi les conseils de BrunoC et suis parvenu, après plusieurs jours de lecture (forum et autres) à obtenir  le résultat souhaité
au problème de date & heure différents selon le système (MVP Rescue media ou Windows10) depuis lequel le démarrage était effectué.

Je dois dire que la tache n'était pas très simple car le diaporama (rescue builder overview.pps) est effectué avec la version 1.2.2
alors que j'utilisais la version MVP Assistant 2.6.3

J'ai donc rencontré quelques problèmes que j'ai résolu plus ou moins facilement.
    Par exemple pour créer le projet, j'ai dû créer le répertoire du projet (PE218B) dans M:\Rescue Builds
    directement avec l'explorateur windows

Une autre difficulté s'est présentée avec l'application Acronis 2018
qui était affichée comme (unable to install Acronis 2018)
J'ai trouvé la solution, fournie par Steve Smith, dans le forum
    MVP V2.6.1 Rescue Tab Show "Acronis True Image 2018..Unable to install this version"!

Il m'a ensuite été possible de créer un fichier .Wim à partir de Acronis media builder et de finaliser la création de la clé USB "MVP_Rescue"

Je vous joins le fichier Log du projet PE2018B

Je vous joins le fichier "PE2018B project.jpg"  image de la configuration
qui me laisse perplexe car le système est affiché
    Microsoft Windows recovery environment(x64)
    index 1
    Built Windows10-1703

alors que mon PC est windows 10 version 2004 (build 19041.1415)

Une remarque
    L'interface utilisateur de MVP_Rescue ne reprend pas les dossiers     administrative tools, programs et SetRes de la version ACRONIS MVP FORUM (je vous joints les images ClipBoard01.jpg, Clipoard02.jpg et ClipBoard03.jpg).
    Est-ce une impossibilité technique ou une évolution à venir ?

J'en arrive ici à essayer de vous transmettre le premier fichier log (BuildISO.log) mais j'ai un message  :
 "le fichier,a pas pu être transféré"
dont je ne comprends pas la raison.

Alemax wrote:

I followed the advice of BrunoC and managed, after several days of reading (forum and others) to obtain the desired result to the problem of different date & time depending on the system (MVP Rescue media or Windows10) from which the boot was made.

I must say that the task was not very simple because the slideshow (rescue builder overview.pps) is done with version 1.2.2
while I was using MVP Assistant version 2.6.3

So I encountered some problems that I solved more or less easily.
     For example to create the project, I had to create the project directory (PE218B) in M:\Rescue Builds
     directly with windows explorer

Another difficulty arose with the Acronis 2018 application which was displayed as (unable to install Acronis 2018)
I found the solution, provided by Steve Smith, in the forum
     MVP V2.6.1 Rescue Tab Show "Acronis True Image 2018..Unable to install this version"!

It was then possible for me to create a .Wim file from Acronis media builder and to finalize the creation of the "MVP_Rescue" USB key

I am attaching the Log file of the PE2018B project

I attach the file "PE2018B project.jpg" image of the configuration which puzzles me because the system is displayed
     Microsoft Windows recovery environment(x64)
     index 1
     Built Windows 10-1703

while my PC is windows 10 version 2004 (build 19041.1415)

An observation
     The MVP_Rescue user interface does not include the administrative tools, programs and SetRes folders of the ACRONIS MVP FORUM version (I attach the images ClipBoard01.jpg, Clipoard02.jpg and ClipBoard03.jpg).
     Is this a technical impossibility or a development to come?

I come here to try to send you the first log file (BuildISO.log) but I have a message:
  "The file could not be transferred"
the reason for which I don't understand.

 

Alemax, I am pleased to hear you got this together. I will try to address some of the issues you brought up.

Yes, the PowerPoint is old and was done as an introduction to the Rescue Builder component when I first released it. Unfortunately, I don't really have the time to prepare a new version. But as releases are done I do update the included Help so hopefully that can provide some additional information.

I am working on version 2.6.4 in which I put in a time zone configuration so that the resultant media will be in your correct time zone and that should address the file date/time issue.

As to the project directory... in the Settings you specify a base folder for rescue projects. When you create a New project, you should be able to create a new subdirectory right from the Windows dialog box. You should not need to do that from Explorer.

Versions of ATI prior to 2019 use a slightly different approach to installation and I have not implemented that. But what I did do is make it very easy to incorporate the usage of the ATI media builder tool by selecting the Acronis wim option in the Image/Source box and just follow the directions.

I am very surprised that your media is Windows 10-1703. Since you are using the version created by Acronis' Media Builder, I am wondering if it has picked up an older WinRE incorrectly. I have seen this in the past. It is possible you have more than one Recovery partition. If you open the Image/Source box, it will probably say you have build 15063. I suggest looking at the System Configuration page of the MVP Assistant where the top pane will tell you where the WinRE partition is located and what build it is. If you do not see a WinRE entry, you may need to fix this with Reagentc. I had an old system updated from Windows 7 and it had this issue. I ended up having to change that old partition so Acronis would not find it. If it comes to that, I can go back in my records to see what I did. An alternative is to download the Windows ADK with the WinPE add-on and use that from the Acronis builder.

I do not understand your observation about the administration tools, etc. A lot of the tools are built in. Perhaps you can be more specific as to what you want.

Try changing the .log file to .txt to see if can be put on the forum.

-Bruno

BrunoC wrote:

Alemax wrote:

I followed the advice of BrunoC and managed, after several days of reading (forum and others) to obtain the desired result to the problem of different date & time depending on the system (MVP Rescue media or Windows10) from which the boot was made.

I must say that the task was not very simple because the slideshow (rescue builder overview.pps) is done with version 1.2.2
while I was using MVP Assistant version 2.6.3

So I encountered some problems that I solved more or less easily.
     For example to create the project, I had to create the project directory (PE218B) in M:\Rescue Builds
     directly with windows explorer

Another difficulty arose with the Acronis 2018 application which was displayed as (unable to install Acronis 2018)
I found the solution, provided by Steve Smith, in the forum
     MVP V2.6.1 Rescue Tab Show "Acronis True Image 2018..Unable to install this version"!

It was then possible for me to create a .Wim file from Acronis media builder and to finalize the creation of the "MVP_Rescue" USB key

I am attaching the Log file of the PE2018B project

I attach the file "PE2018B project.jpg" image of the configuration which puzzles me because the system is displayed
     Microsoft Windows recovery environment(x64)
     index 1
     Built Windows 10-1703

while my PC is windows 10 version 2004 (build 19041.1415)

An observation
     The MVP_Rescue user interface does not include the administrative tools, programs and SetRes folders of the ACRONIS MVP FORUM version (I attach the images ClipBoard01.jpg, Clipoard02.jpg and ClipBoard03.jpg).
     Is this a technical impossibility or a development to come?

I come here to try to send you the first log file (BuildISO.log) but I have a message:
  "The file could not be transferred"
the reason for which I don't understand.

 

Alemax, I am pleased to hear you got this together. I will try to address some of the issues you brought up.

Yes, the PowerPoint is old and was done as an introduction to the Rescue Builder component when I first released it. Unfortunately, I don't really have the time to prepare a new version. But as releases are done I do update the included Help so hopefully that can provide some additional information.

I am working on version 2.6.4 in which I put in a time zone configuration so that the resultant media will be in your correct time zone and that should address the file date/time issue.

As to the project directory... in the Settings you specify a base folder for rescue projects. When you create a New project, you should be able to create a new subdirectory right from the Windows dialog box. You should not need to do that from Explorer.

Versions of ATI prior to 2019 use a slightly different approach to installation and I have not implemented that. But what I did do is make it very easy to incorporate the usage of the ATI media builder tool by selecting the Acronis wim option in the Image/Source box and just follow the directions.

I am very surprised that your media is Windows 10-1703. Since you are using the version created by Acronis' Media Builder, I am wondering if it has picked up an older WinRE incorrectly. I have seen this in the past. It is possible you have more than one Recovery partition. If you open the Image/Source box, it will probably say you have build 15063. I suggest looking at the System Configuration page of the MVP Assistant where the top pane will tell you where the WinRE partition is located and what build it is. If you do not see a WinRE entry, you may need to fix this with Reagentc. I had an old system updated from Windows 7 and it had this issue. I ended up having to change that old partition so Acronis would not find it. If it comes to that, I can go back in my records to see what I did. An alternative is to download the Windows ADK with the WinPE add-on and use that from the Acronis builder.

I do not understand your observation about the administration tools, etc. A lot of the tools are built in. Perhaps you can be more specific as to what you want.

Try changing the .log file to .txt to see if can be put on the forum.

-Bruno

 

 

Your announcement of working on a version 2.6.4 seems very interesting to me and I will come back to it in the next lines.

Your answer allowed me to see that I had made some handling mistakes especially about the project directory that works actually very well with the Windows dialog box

About the media
It is indeed Windows 10-1703. So I have, as you indicate, open the Image/Source box, and it is version 15063. I then looked at the System Configuration page of the MVP wizard where the top pane will tell where the WinRE partition is located and which generation it is: I didn't see a WinRE entry.

Having never used Reagentc, after looking at the possibilities and parameters I preferred to abstain and used the alternative you indicated.
I used from the Acronis generator. Windows ADK with WinPE add-on.

This is where I come back to your future version 2.6.4:
Indeed the version I created above must be by default the time zone at GMT-8, your reply to my post of 11/06/2023.

About the admin tools, etc. I'm sorry I wasn't clearer but it's related to my last remark about the .log file that I was unable to transfer to you.
In fact I had tried to transfer you one after the other (I attach you...
I am attaching the Log file of the PE2018B project
I attach the file 'PE2018B project.jpg'
I attach the images ClipBoard01.jpg, Clipoard02.jpg and ClipBoard03.jpg)

I come here to try to send you the first log file (BuildISO.log) but I have a message:
 'The file could not be uploaded'
I do not understand why.
I just tried again to send you one by one the "I attach file"  with the error
"The file could not be uploaded"

One last question about version 2.6.4
You have set a time zone configuration so that the resulting media is in the correct time zone.
What about daylight saving time (active on Windows 10 system)

Concerning the old WinRE version...

1. Please look at C:\Windows\System32\Recovery. Do you have a WinRE.wim file located there? Take a look at the ReAgent.xml file located there. It should tell where WinRE.wim is located. On mine, there is a line that says
  <WinreLocation path="\Recovery\WindowsRE" id="0" offset="499211304960" guid="{e3696bab-96a1-4a3f-bbc9-7c9063081f1c}"/>

In my case, the guid is the id of my system drive. In the MVP Assistant System Configuration, select the system drive and you will see its GUID. The offset matches the offset of the partition which contains WinRE.wim and that parition should show Type: GPT  Microsoft Recovery  (WinRE). [I am assuming GPT, not MBR disk.]

If it looks like WinRE is actually on a partition, you can sometimes fix this by running these commands as Admin. If you already see the .wim file in the C:\Windows\System32\Recovery folder, then the disable may not be needed.
Reagentc /disable
Reagentc /enable

If all gets put right, then the WinRE partition should show up in the top pane in the MVP Assistant. Here is how mine looks.

Operating System:  Microsoft Windows 10 Pro,  Version 22H2,  Build 10.0.19045.2965,  64-bit
Build ID:                   19041.1.amd64fre.vb_release.191206-1406
Installed:                  11/23/2020 2:31:16 PM
Last Boot:                6/21/2023 8:02:54 AM
Boot:                         Disk 2  Partition 2
WinRE:                      Disk 2  Partition 5  (Build 19041)
BIOS Mode:             UEFI  (Secure Boot Disabled)

EDIT:

Also, if you open your MVP Assistant rescue build project which used the wrong WinRE, look at the top left pane to see what it says for Wim source. On mine I see

Wim source:    WinRE: \\?\Volume{28635cbb-3d24-4f12-baca-95e152c487f2}\Recovery\WindowsRE\winre.wim

The guid next to the Volume is that GUID for Disk 2 Partition 5 as shown as the WinRE location.

BrunoC wrote:

Concerning the old WinRE version...

1. Please look at C:\Windows\System32\Recovery. Do you have a WinRE.wim file located there? Take a look at the ReAgent.xml file located there. It should tell where WinRE.wim is located. On mine, there is a line that says
  <WinreLocation path="\Recovery\WindowsRE" id="0" offset="499211304960" guid="{e3696bab-96a1-4a3f-bbc9-7c9063081f1c}"/>

In my case, the guid is the id of my system drive. In the MVP Assistant System Configuration, select the system drive and you will see its GUID. The offset matches the offset of the partition which contains WinRE.wim and that parition should show Type: GPT  Microsoft Recovery  (WinRE). [I am assuming GPT, not MBR disk.]

If it looks like WinRE is actually on a partition, you can sometimes fix this by running these commands as Admin. If you already see the .wim file in the C:\Windows\System32\Recovery folder, then the disable may not be needed.
Reagentc /disable
Reagentc /enable

If all gets put right, then the WinRE partition should show up in the top pane in the MVP Assistant. Here is how mine looks.

Operating System:  Microsoft Windows 10 Pro,  Version 22H2,  Build 10.0.19045.2965,  64-bit
Build ID:                   19041.1.amd64fre.vb_release.191206-1406
Installed:                  11/23/2020 2:31:16 PM
Last Boot:                6/21/2023 8:02:54 AM
Boot:                         Disk 2  Partition 2
WinRE:                      Disk 2  Partition 5  (Build 19041)
BIOS Mode:             UEFI  (Secure Boot Disabled)

EDIT:

Also, if you open your MVP Assistant rescue build project which used the wrong WinRE, look at the top left pane to see what it says for Wim source. On mine I see

Wim source:    WinRE: \\?\Volume{28635cbb-3d24-4f12-baca-95e152c487f2}\Recovery\WindowsRE\winre.wim

The guid next to the Volume is that GUID for Disk 2 Partition 5 as shown as the WinRE location.

There seems to be a problem with my message waiting for validation
which appears however 21/06/2023 at 16:03 but to which you have not responded and send me this message about the old version of WINRE.

I performed the requested operation on C:Windows\system32\Recovery and I have read the ReAgentX.ml file
I make a copy of its contents and attach it to you below (I still can not attach files, please see the missed message of 21/06/2023)

<WindowsRE version="2.0">
    <WinreBCD id=""></WinreBCD>
    <WinreLocation path="" id="0" offset="0"></WinreLocation>
    <ImageLocation path="" id="0" offset="0"></ImageLocation>
    <PBRImageLocation path="" id="0" offset="0" index="0"></PBRImageLocation>
    <PBRCustomImageLocation path="" id="0" offset="0" index="0"></PBRCustomImageLocation>
    <InstallState state="0"></InstallState>
    <OsInstallAvailable state="0"></OsInstallAvailable>
    <CustomImageAvailable state="0"></CustomImageAvailable>
    <WinREStaged state="0"></WinREStaged>
    <ScheduledOperation state="4"></ScheduledOperation>
    <OperationParam path=""></OperationParam>
    <OperationPermanent state="0"></OperationPermanent>
    <OsBuildVersion path=""></OsBuildVersion>
    <OemTool state="0"></OemTool>
</WindowsRE>

This looks off to me. What response do you get to reagentc /info command?

Have you looked into all the partitions on your system disk? The MVP Assistant provides some information. Also, Windows DIsk Management can show things.

I am wondering if there is a partition which contains the correct version of WinRE.

BrunoC wrote:

This looks off to me. What response do you get to reagentc /info command?

Have you looked into all the partitions on your system disk? The MVP Assistant provides some information. Also, Windows DIsk Management can show things.

I am wondering if there is a partition which contains the correct version of WinRE.

 Je vous transmets ci-après le résultat de la commande reagentC /info.

C:\WINDOWS\system32>reagentC /info
Informations sur la configuration de l’Environnement de récupération
Windows (WinRE) et la réinitialisation du système:

    État WinRE :Enabled
    Emplacement WinRE: \\?\GLOBALROOT\device\harddisk4\partition3\Recovery\WindowsRE
    Identificateur des données de configuration du démarrage (BCD): bede9aaf-0259-11eb-9a3f-bcaec52cc057
    Emplacement de l’image de récupération:
    Index de l’image de récupération:       0
    Emplacement de l’image personnalisée:
    Index de l’image personnalisée:         0

REAGENTC.EXE: opération réussie.

Pour résoudre le problème vous aviez indiqué dans un précédent message

"An alternative is to download the Windows ADK with the WinPE add-on and use that from the Acronis builder."

C'est ce que j'ai réalisé :  je vous joins ci-dessous un copié du résultat car il est toujours impossible de joindre un fichier

    Project Name:    PE2018C
    Description:    Tentative création
    Location:    M:\Rescue builds\PE2018C\
    Language:    fr-fr
    Wim source:    M:\Depuis ADK+PE\AcronisBootablePEMedia.wim
    Image:    Microsoft Windows PE (x64)
    Index:    1
    Build:    Windows 10-2004
    Bootable:    Yes
    Installation:    WindowsPE
    Mounted:    No

J'ai ensuite créé le média comme indiqué. Cette version présente juste le problème que le media résultant ne soit pas dans la zone de temps correcte (la version 2.6.4 sur laquelle vous travaillez devrait permettre de résoudre ce problème )

Alemax wrote:

 

J'ai ensuite créé le média comme indiqué. Cette version présente juste le problème que le media résultant ne soit pas dans la zone de temps correcte (la version 2.6.4 sur laquelle vous travaillez devrait permettre de résoudre ce problème )

I then created the media as instructed. This version just has the problem that the resulting media is not in the correct time zone (the 2.6.4 version you are working on should fix this problem)

Alemax, did you get a chance to try version 2.7.0.2? Has it helped with the time zone issue?

Hello Bruno
My response was slow because I realized that with Acronis TI2018 I will probably always be
blocked because of the constraints it imposes
I tried to install an Acronis TI2021 version, but in this case ACRONIS imposes the purchase of
an AcronisCyberProtectHomeOffice license that will only work with a subscription
 (while I have a perpetual 3-seat license with TI2018).

So I bought an AcronisCyberProtectHomeOffice 2023 license and installed it on one of the
my PC's test systems.
On the PC my 3 windows 10 systems had remained in version 2004 (19041.1415) and I very
quickly understood that I will not escape the update to Windows 10 2022 version 22H2 (19045.3271)
currently.

Most of the work is done on this PC, and I was able to start working with it.
MVP ASSISTANT version 7.0.2

In short
For the creation of Rescue media, I indicated in WIM source ADK WINPE, and went through
the different steps that allowed me to create a bootable and operational MSP_RESCUE key

The time zone management for the resulting media is almost perfect (-1h)
because daylight saving time is active on the Windows 10 system of the PC.
Would a setting be possible?

I still have to review
-1 The problem of the WINRE version (I followed a tutorial that seemed quite approximate to me) and which obviously didn't work.
-2 I tried to integrate into the key MVP_RESCUE  
tthe AcronisCyberProtectHomeOffice universal restore application
- or in the .XML file that is presented when adding the application, is noted
"' NOTE: Only 64-bit executables will run on the rescue media"
By the way, the version I got is a .MSI file (not a .exe)
"AcronisCyberProtectHomeOffice_ur_en-US.msi"
This installation therefore seems impossible to me.

Is there another solution to use universal restore ?
(I was planning an installation on a PC with an ASUS SABERTOOTH X58 motherboard)

Thanks in advance
Alemax

PS

J'en arrive ici à essayer de vous transmettre un fichier log BuildProject.log mais j'ai un message  :
 "le fichier,a pas pu être transféré"
dont je ne comprends pas la raison.

Idem avec une copie d'écran de "rescue media"

See forum topic: How to create ACPHO rescue media with AUR included 

The issue with uploading files is a continuing one with the forum software - sometimes it may work otherwise it is broken, the same with embedding images!!

The best method to share such files is to put them in a cloud share location using such as OneDrive, Dropbox, Google Drive etc, then either post the share link or sent it to Bruno (or other MVP's) via a private message.

Note: to post a link in the forum may require obscuring the link, i.e. add spaces to render the link non-clickable!

Bonjour Steve,
Votre tutoriel m'a été d'une grande utilité bien que j'ai eu des interrogations car je travaille actuellement avec la version MVP ASSISTANT 2.7.0.2 et  j'ai dû m'adapter!

Je vous ai transmis via WeTransfer un fichier.zip avec Logs, screenShot

Pour récupérer ce fichier j'ai tenté de vous mettre le lien comme non cliquable we.tl /t-0h0g35d  Y9O
comme indiqué

J'ai rendu le lien https:// non cliquable comme indiqué

.

Your tutorial was very useful to me although I had questions because I am currently working with the MVP ASSISTANT 2.7.0.2 version and I had to adapt!

I sent you via WeTransfer a .zip file with Logs, screenShot

To recover this file I tried to put the link as not clickable we.tl /t-0h0g35d Y9O
as indicated

I made the https:// link unclickable as shown

I downloaded the zip file from https://we.tl/t-0h0g35dY9O and took a quick look at the logs etc but do not see any obvious issues?  

Steve Smith wrote:

Your tutorial was very useful to me although I had questions because I am currently working with the MVP ASSISTANT 2.7.0.2 version and I had to adapt!

I sent you via WeTransfer a .zip file with Logs, screenShot

To recover this file I tried to put the link as not clickable we.tl /t-0h0g35d Y9O
as indicated

I made the https:// link unclickable as shown

I downloaded the zip file from (my link) and took a quick look at the logs etc but do not see any obvious issues?  

I just removes the https link because of message "You are not allowed to place hyperlinks inside the text, please, clear them."

My answer :

Same for me.
I had a trouble ticket with Acronis
'We are following up on your trouble ticket #06013847 AcronisCyberProtectHomeOffice_ur_en-US."
and given the result obtained with your help, I told them the problem was solved,