ACPHO update 40729 rescue media error
Until now, I was using the ACPHO version 40338 ,
with MVP_Assistant 2.7.4.0
An outstanding problem :
Since I was using ACPHO 40338
So I naively thought that the directory should have been::
ProgramFiles/Acronis/BackupAndRecovery.
I was informed that an update 40729 from ACPHO was available and that I could take advantage of it.
So I got to work and used only MVP_ASSISTANT 2.7.4.0 to create the backup media.
I created a new AUR source. Wim for this version of ACPHO 40729 and have integrated the AUR.XML file used in version 40338 following the advice of BrunoC
I then proceeded to the creation of a new project, the assembly from the source AUR. Wim , settings rescue media and advanced configuration for setting up AURButton
I installed the queued applications, performed a commit
Exploration has shown that the ProgramFiles/Acronis/BackupAndRecovery still did not exist.
I then did an unmount and then the creation of the ISO image
I then updated my USB stick with the image. .ISO
I started from the USB Stick
When starting WinPE, the launch bar is as I expected but no ACPHO window 40729 but an error
'Failed to open the application component
Please resinstall Acronis Cyber protect home office'
I took a screenshot
- of the error displayed
- of the launch bar
- f the AUR window
Here after a copy of the BuildProject.log
------------ Begin Logging Session (Builder version 2.7.4.0) ------------
10-01-2023 08:30:40 Info Project created in folder M:\MVP_ASS_2-7-4-0\Rescue builds\ACPHO_AUR_0\
10-01-2023 08:30:40 Info Running in Advanced Mode
10-01-2023 08:31:47 Info WIM Source .wim file: M:\Acronis AUR Media\AUR.XML file contents ACPHO #40729\AUR.wim
10-01-2023 08:31:47 Info Acquiring .wim file to project ...
10-01-2023 08:31:50 Info Successfuly acquired .wim file to project.
10-01-2023 08:44:56 Info Mounting image file...
10-01-2023 08:45:04 Info Scanning image for applications and packages...
------------ Begin Logging Session (Builder version 2.7.4.0) ------------
10-01-2023 08:51:20 Info Configuration loaded from M:\MVP_ASS_2-7-4-0\Rescue builds\ACPHO_AUR_0
10-01-2023 08:51:20 Info Running in Advanced Mode
10-01-2023 08:51:57 Info Unmounting image...
10-01-2023 08:52:00 Info Setting image language to fr-fr
10-01-2023 08:52:15 Info Image successfully unmounted
10-01-2023 08:53:05 Info Mounting image file...
10-01-2023 08:53:13 Info Scanning image for applications and packages...
10-01-2023 08:53:16 Info Checking for shell application...
10-01-2023 08:53:16 Info Installing Boot Initialization
10-01-2023 08:53:17 Info Installing Icons
10-01-2023 08:53:17 Info Installing SetMon Utility
10-01-2023 08:53:17 Info Installing IrfanView Graphic Viewer
10-01-2023 08:53:17 Info Installing Power Button
10-01-2023 08:53:17 Info Installing Command Prompt Button
10-01-2023 08:53:17 Info Installing Registry Editor Button
10-01-2023 08:53:17 Info Installing Task Manager Button
10-01-2023 08:53:17 Info Installing Launch Bar
10-01-2023 08:53:18 Info Checking for required packages...
10-01-2023 08:53:18 Info Installing language package fr-FR...
10-01-2023 08:53:58 Info Installing package WinPE-WMI...
10-01-2023 08:54:06 Info Installing package WinPE-WMI for fr-FR...
10-01-2023 08:54:10 Info Installing package WinPE-Scripting...
10-01-2023 08:54:11 Info Installing package WinPE-Scripting for fr-FR...
10-01-2023 08:54:12 Info Installing package WinPE-EnhancedStorage...
10-01-2023 08:54:14 Info Installing package WinPE-EnhancedStorage for fr-FR...
10-01-2023 08:54:16 Info Installing package WinPE-SecureStartup...
10-01-2023 08:54:17 Info Installing package WinPE-SecureStartup for fr-FR...
10-01-2023 08:54:20 Info Image successfully mounted
10-01-2023 08:55:11 Info Committing image changes...
10-01-2023 08:55:14 Info Setting image language to fr-fr
10-01-2023 08:55:16 Info Setting image time zone to (UTC+01:00) Bruxelles, Copenhague, Madrid, Paris
10-01-2023 08:55:25 Info Changes successfully committed
10-01-2023 08:56:27 Info Installing Monitor Settings Utility Button
10-01-2023 08:56:27 Info Installing Acronis Cyber Protect Home Office Build 40729
10-01-2023 08:56:31 Info Installing Acronis Universal Restore Button
10-01-2023 08:56:31 Info Installing IrfanView Graphic Viewer
10-01-2023 08:56:31 Info Installing A43 File Management Utility
10-01-2023 08:56:31 Info Installing PE Network
10-01-2023 08:56:32 Info Installing Notepad++ Text Editor
10-01-2023 08:56:33 Info Application installations completed
10-01-2023 08:57:01 Info Application installations completed
10-01-2023 08:57:11 Info Committing image changes...
10-01-2023 08:57:21 Info Changes successfully committed
10-01-2023 08:58:10 Info Unmounting image...
10-01-2023 08:58:30 Info Image successfully unmounted
10-01-2023 08:58:51 Info Preparing media
10-01-2023 08:58:52 Info Installing Unattend.xml
10-01-2023 08:58:52 Info Preventing media from booting in UEFI mode
10-01-2023 08:58:52 Info Successfully created ISO
10-01-2023 08:58:59 Info Project closed
------------ Begin Logging Session (Builder version 2.7.4.0) ------------
10-01-2023 08:59:43 Info Configuration loaded from M:\MVP_ASS_2-7-4-0\Rescue builds\ACPHO_AUR_0
10-01-2023 08:59:43 Info Running in Advanced Mode
10-01-2023 09:02:12 Info Project closed
------------ Begin Logging Session (Builder version 2.7.4.0) ------------
10-01-2023 14:33:39 Info Configuration loaded from M:\MVP_ASS_2-7-4-0\Rescue builds\ACPHO_AUR_0
10-01-2023 14:33:39 Info Running in Advanced Mode
10-01-2023 14:34:29 Info Project closed
------------ Begin Logging Session (Builder version 2.7.4.0) ------------
10-01-2023 16:03:56 Info Configuration loaded from M:\MVP_ASS_2-7-4-0\Rescue builds\ACPHO_AUR_0
10-01-2023 16:03:56 Info Running in Advanced Mode
10-01-2023 16:27:56 Info Project closed
Alemax, when you update ACPHO this does not automatically update your AUR.
I suggest you uninstall AUR and then reinstall it by selecting the AUR tool from ACPHO. Then recreate the AUR wim to see if that helps.
You say you created a Universal Restore media. Can that media boot into the Universal Restore program? You say when you use the AUR wim as the source for an MVPAssistant project, mount the image and explore the image \Program Files\Acronis\BackupAndRecovery doesn't exist. What folders do you see under \Program Files\Acronis?
Mustang wrote:You say you created a Universal Restore media. Can that media boot into the Universal Restore program? You say when you use the AUR wim as the source for an MVPAssistant project, mount the image and explore the image \Program Files\Acronis\BackupAndRecovery doesn't exist. What folders do you see under \Program Files\Acronis?
Folders under Program Files\Acronis
AURButton
CyberProtectHomeOffice
UniversalRestore
Folders under Program Files\Acronis
AURButton
CyberProtectHomeOffice
UniversalRestore
The above shows you have an older version of AUR installed so you need to use the following AUR.XML file to create the correct AUR launch button depending on which version of AUR is found.
<?xml version="1.0" encoding="utf-8"?>
<Applications>
<App name="AURButton" description="Acronis Universal Restore Button" sharedprogramfolder="Acronis" visible="yes" optional="yes" autoinstall="no">
<Install>
<LaunchButton name="AUR" command="%ProgramFiles%\Acronis\BackupAndRecovery\trueimage_starter.exe" args=" " iconfile="%ProgramFiles%\Acronis\BackupAndRecovery\TrueImage.exe" iconindex="" />
<LaunchButton name="AUR" command="%ProgramFiles%\Acronis\UniversalRestore\trueimage_starter.exe" args=" " iconfile="%ProgramFiles%\Acronis\UniversalRestore\TrueImage.exe" iconindex="" />
</Install>
<Uninstall>
<DeleteProgramFolder />
</Uninstall>
</App>
</Applications>
Steve is right. You have the older version of UR installed. If you want to upgrade to the new version, you need to uninstall UR first. Then try to run the UR media builder again. You will be directed to a download page. Select the 64 bit version to download. Install the new version and create the recovery media again. Now you will see the \Program Files\Acronis\BackupAndRecovery folder instead of the UniversalRestore folder when you create a new project with MVPAssistant.
Mustang wrote:Steve is right. You have the older version of UR installed. If you want to upgrade to the new version, you need to uninstall UR first. Then try to run the UR media builder again. You will be directed to a download page. Select the 64 bit version to download. Install the new version and create the recovery media again. Now you will see the \Program Files\Acronis\BackupAndRecovery folder instead of the UniversalRestore folder when you create a new project with MVPAssistant.
Part 1
I performed in order
1 Uninstalling UR
2 Installation of UR
3 from ACPHO 40729 -> tools
Acronis Universal restore
Acronis media builder
Part 2
Since MVP 2.7.4.0
Creating a new project ACPHO_AUR_4
Project setting advanced customization
I recreated the AURButton button
then imported by replacing the AUR.xml file with the one recommended and written by Steve.
Part 3
Project Rescue media
source image
I import the AUR.wim file created in Part 1
When there are no more pending updates
I'm running Image Explore but I've always
in Programs\acronis directories
AURButton
CyberProtectHomeOffice
Universal restore
Here After BuildProject.Log
------------ Begin Logging Session (Builder version 2.7.4.0) ------------
10-03-2023 15:07:59 Info Project created in folder M:\MVP_ASS_2-7-4-0\Rescue builds\ACPHO_AUR_4\
10-03-2023 15:07:59 Info Running in Advanced Mode
10-03-2023 15:16:02 Info Project closed
------------ Begin Logging Session (Builder version 2.7.4.0) ------------
10-03-2023 15:16:02 Info Configuration loaded from M:\MVP_ASS_2-7-4-0\Rescue builds\ACPHO_AUR_4
10-03-2023 15:16:02 Info Running in Advanced Mode
10-03-2023 15:16:50 Info WIM Source .wim file: M:\Acronis AUR Media\AUR.XML file contents ACPHO #40729\AUR.wim
10-03-2023 15:16:50 Info Acquiring .wim file to project ...
10-03-2023 15:16:50 Info Successfuly acquired .wim file to project.
10-03-2023 15:17:25 Info Mounting image file...
10-03-2023 15:17:34 Info Scanning image for applications and packages...
10-03-2023 15:17:38 Info Checking for shell application...
10-03-2023 15:17:38 Info Installing Boot Initialization
10-03-2023 15:17:38 Info Installing Icons
10-03-2023 15:17:39 Info Installing SetMon Utility
10-03-2023 15:17:39 Info Installing IrfanView Graphic Viewer
10-03-2023 15:17:39 Info Installing Power Button
10-03-2023 15:17:39 Info Installing Command Prompt Button
10-03-2023 15:17:39 Info Installing Registry Editor Button
10-03-2023 15:17:39 Info Installing Task Manager Button
10-03-2023 15:17:39 Info Installing Launch Bar
10-03-2023 15:17:40 Info Checking for required packages...
10-03-2023 15:17:40 Info Installing language package fr-FR...
10-03-2023 15:18:18 Info Installing package WinPE-WMI...
10-03-2023 15:18:25 Info Installing package WinPE-WMI for fr-FR...
10-03-2023 15:18:29 Info Installing package WinPE-Scripting...
10-03-2023 15:18:30 Info Installing package WinPE-Scripting for fr-FR...
10-03-2023 15:18:31 Info Installing package WinPE-EnhancedStorage...
10-03-2023 15:18:33 Info Installing package WinPE-EnhancedStorage for fr-FR...
10-03-2023 15:18:34 Info Installing package WinPE-SecureStartup...
10-03-2023 15:18:35 Info Installing package WinPE-SecureStartup for fr-FR...
10-03-2023 15:18:38 Info Image successfully mounted
10-03-2023 15:19:18 Info Committing image changes...
10-03-2023 15:19:20 Info Setting image language to fr-fr
10-03-2023 15:19:22 Info Setting image time zone to (UTC+01:00) Bruxelles, Copenhague, Madrid, Paris
10-03-2023 15:19:31 Info Changes successfully committed
10-03-2023 15:21:03 Info Installing Monitor Settings Utility Button
10-03-2023 15:21:03 Info Installing Acronis Cyber Protect Home Office Build 40729
10-03-2023 15:21:07 Info Installing A43 File Management Utility
10-03-2023 15:21:07 Info Installing PE Network
10-03-2023 15:21:08 Info Installing IrfanView Graphic Viewer
10-03-2023 15:21:08 Info Installing Notepad++ Text Editor
10-03-2023 15:21:10 Info Installing Acronis Universal Restore Button
10-03-2023 15:21:10 Info Application installations completed
10-03-2023 15:47:06 Info Committing image changes...
10-03-2023 15:47:17 Info Changes successfully committed
10-03-2023 16:19:07 Info Project closed
One more question
Two days ago i tried to create a rescue media using WINRE
I took a snapshot of the result which I produce here
Source File: AcronisWIMMedia.wim
Type: Wim
Name: Microsoft Windows Recovery Environment (x64)
Index: 1
Edition: WindowsPE
Architecture: AMD64
Bootable: Yes
Build: 10.0.15063.0 (Windows 10-1703)
Service Pack Level: o
languages: fr-FR (Default)Created: 20/03/2017 02:14:36
Modified: 02/10/2023 17:15:06
So it seems the recovery partion of my C drive is not OK
could it be a problem for ACPHO installation .?
Regards
Alemax
Alemax, you are definitely including the older version of Univeral Restore. I have just tested on my system and just like Steve it all was correct.
Let me go through the steps again.
1. Uninstall Acronis Universal Restore.
2. From ACPHO Tools, select Acronis Universal Restore. Since it does not see Universal Restore installed, it should give you the page with a Download button. Click Download and select the Windows 64-bit version. Save the file, overwriting an prior version you may have had. The downloaded installer was version 15.0.1.30655.
3. Execute the downloaded file to run the Universal Restore Setup.
4. Go back to ACPHO Tools and select Acronis Universal Restore again. This time you get the bootable media builder wizard. Be sure to select media type as Windows PE (64-bit) and then Create WinRE based media. Follow through the Wizard to produce a WIM image.
5. In the MVP Assistant, create a new project and for the Image Source, select Local wim. Be sure to select the wim you just built in step 4.
If this does not get you the right folder, then there may be other factors at play here
Maybe you don't get the same downloads as us because you're building on a French system. We're building on English US systems. When you look in Control Panel/Programs and Features, what version of Acronis Universal Restore do you see? I see 15.0.30655.
BrunoC wrote:Alemax, you are definitely including the older version of Univeral Restore. I have just tested on my system and just like Steve it all was correct.
Let me go through the steps again.
1. Uninstall Acronis Universal Restore.
2. From ACPHO Tools, select Acronis Universal Restore. Since it does not see Universal Restore installed, it should give you the page with a Download button. Click Download and select the Windows 64-bit version. Save the file, overwriting an prior version you may have had. The downloaded installer was version 15.0.1.30655.
I had to uninstall universal restore from windows setting application
to have access to the download button3. Execute the downloaded file to run the Universal Restore Setup.
4. Go back to ACPHO Tools and select Acronis Universal Restore again. This time you get the bootable media builder wizard. Be sure to select media type as Windows PE (64-bit) and then Create WinRE based media. Follow through the Wizard to produce a WIM image.
I created a WINPE media because
it seems the recovery partition of my C drive is not OK :
Build: 10.0.15063.0 (Windows 10-1703)
5. In the MVP Assistant, create a new project and for the Image Source, select Local wim. Be sure to select the wim you just built in step 4.
If this does not get you the right folder, then there may be other factors at play here
It is the right folder
Here after the Build Project.Log
------------ Begin Logging Session (Builder version 2.7.4.0) ------------
10-04-2023 09:52:13 Info Project created in folder M:\MVP_ASS_2-7-4-0\Rescue builds\ACPHO_AUR_2\
10-04-2023 09:52:13 Info Running in Advanced Mode
10-04-2023 09:55:46 Info Project closed
------------ Begin Logging Session (Builder version 2.7.4.0) ------------
10-04-2023 09:55:46 Info Configuration loaded from M:\MVP_ASS_2-7-4-0\Rescue builds\ACPHO_AUR_2
10-04-2023 09:55:46 Info Running in Advanced Mode
10-04-2023 09:56:46 Info WIM Source .wim file: M:\Acronis AUR Media\AUR.XML file contents ACPHO #40729\AUR.wim
10-04-2023 09:56:46 Info Acquiring .wim file to project ...
10-04-2023 09:56:50 Info Successfuly acquired .wim file to project.
10-04-2023 09:57:11 Info Mounting image file...
10-04-2023 09:57:27 Info Scanning image for applications and packages...
10-04-2023 09:57:31 Info Checking for shell application...
10-04-2023 09:57:32 Info Installing Boot Initialization
10-04-2023 09:57:32 Info Installing Icons
10-04-2023 09:57:32 Info Installing SetMon Utility
10-04-2023 09:57:32 Info Installing IrfanView Graphic Viewer
10-04-2023 09:57:32 Info Installing Power Button
10-04-2023 09:57:32 Info Installing Command Prompt Button
10-04-2023 09:57:32 Info Installing Registry Editor Button
10-04-2023 09:57:32 Info Installing Task Manager Button
10-04-2023 09:57:32 Info Installing Launch Bar
10-04-2023 09:57:33 Info Checking for required packages...
10-04-2023 09:57:34 Info Installing language package fr-FR...
10-04-2023 09:57:39 Info Installing package WinPE-EnhancedStorage...
10-04-2023 09:57:42 Info Installing package WinPE-EnhancedStorage for fr-FR...
10-04-2023 09:57:43 Info Installing package WinPE-SecureStartup...
10-04-2023 09:57:44 Info Installing package WinPE-SecureStartup for fr-FR...
10-04-2023 09:57:47 Info Image successfully mounted
10-04-2023 10:01:23 Info Committing image changes...
10-04-2023 10:01:25 Info Setting image time zone to (UTC+01:00) Bruxelles, Copenhague, Madrid, Paris
10-04-2023 10:01:36 Info Changes successfully committed
10-04-2023 10:01:40 Info Installing Monitor Settings Utility Button
10-04-2023 10:01:40 Info Installing Acronis Cyber Protect Home Office Build 40729
10-04-2023 10:01:44 Info Installing Acronis Universal Restore Button
10-04-2023 10:01:44 Info Installing IrfanView Graphic Viewer
10-04-2023 10:01:45 Info Installing A43 File Management Utility
10-04-2023 10:01:45 Info Installing PE Network
10-04-2023 10:01:45 Info Installing Notepad++ Text Editor
10-04-2023 10:01:46 Info Application installations completed
10-04-2023 10:01:56 Info Committing image changes...
10-04-2023 10:02:10 Info Changes successfully committed
10-04-2023 10:03:04 Info Unmounting image...
10-04-2023 10:03:50 Info Preparing media
10-04-2023 10:03:50 Info Installing Unattend.xml
10-04-2023 10:03:38 Info Image successfully unmounted
10-04-2023 10:03:50 Info Preventing media from booting in UEFI mode
10-04-2023 10:03:51 Info Successfully created ISO
10-04-2023 10:05:41 Info Mounting image file...
10-04-2023 10:05:55 Info Scanning image for applications and packages...
10-04-2023 10:05:59 Info Checking for shell application...
10-04-2023 10:05:59 Info Checking for required packages...
10-04-2023 10:06:00 Info Image successfully mounted
10-04-2023 10:06:27 Info Committing image changes...
10-04-2023 10:06:37 Info Changes successfully committed
10-04-2023 10:06:49 Info Application installations completed
10-04-2023 10:07:10 Info Unmounting image...
10-04-2023 10:07:39 Info Image successfully unmounted
10-04-2023 10:08:08 Info Preparing media
10-04-2023 10:08:08 Info Installing Unattend.xml
10-04-2023 10:08:08 Info Preventing media from booting in UEFI mode
10-04-2023 10:08:09 Info Successfully created ISO
10-04-2023 10:09:01 Info Project closed
When starting WinPE from the Usb stick, the launch bar is as I expected but no ACPHO window 40729 but an error
"Failed to open the application component
Please resinstall Acronis Cyber protect home office"
I took a screenshot
- of the error displayed
- of the launch bar
- of the AUR window
but it's unfortunatly not possible here to add files
However I insert a link to image added using lmce File manager
https://forum.acronis.com/sites/default/files/users/user258451/Presse-p…
Thanks to Steve, Mustang and you for your help and patience
Regards
Alemax
Alemax,
Your posted error codes suggest that you're on to something with the idea that your recovery partition is corrupt and causing the problem you have.
I would suggest running SFC /Scannow from an admin Windows Terminal to check for system file errors. If errors are found and fixed run the command repeatedly until no errors are found.
Also I recommend you run DISM /Online /Cleanup-Image /CheckHealth
If errors are found run DISM /Online /Cleanup-Image /RestoreHealth
During the RestoreHealth process if it appears that the process has stopped or is stuck this is normal, just wait for the process to complete.
Post back your results.
Enchantech wrote:Alemax,
Your posted error codes suggest that you're on to something with the idea that your recovery partition is corrupt and causing the problem you have.
I would suggest running SFC /Scannow from an admin Windows Terminal to check for system file errors. If errors are found and fixed run the command repeatedly until no errors are found.
Also I recommend you run DISM /Online /Cleanup-Image /CheckHealth
If errors are found run DISM /Online /Cleanup-Image /RestoreHealth
During the RestoreHealth process if it appears that the process has stopped or is stuck this is normal, just wait for the process to complete.
Post back your results.
Résults
1/ SFC / SCANNOW
----------------
C:\WINDOWS\system32>SFC /SCANNOW
Début de l’analyse du système. Cette opération peut nécessiter un certain temps.
Démarrage de la phase de vérification de l’analyse du système.
La vérification est à 100% terminée.
Le programme de protection des ressources Windows n’a trouvé aucune violation d’intégrité.
Début de l’analyse du système. Cette opération peut nécessiter un certain temps.
Démarrage de la phase de vérification de l’analyse du système.
La vérification est à 100% terminée.
Le programme de protection des ressources Windows n’a trouvé aucune violation d’intégrité.
*****************
2/ DISM /Online ...
--------------------
C:\WINDOWS\system32>DISM /Online /Cleanup-Image /CheckHealth
Outil Gestion et maintenance des images de déploiement
Version : 10.0.19041.844
Version de l’image : 10.0.19045.3448
Aucun endommagement du magasin de composants n’a été détecté.
L’opération a réussi.
**********************
I posted some days ago (03 October 2023):, and I worried about the WINRE build windows 10 version
Two days ago i tried to create a rescue media using WINRE
I took a snapshot of the result which I produce here
Source File: AcronisWIMMedia.wim
Type: Wim
Name: Microsoft Windows Recovery Environment (x64)
Index: 1
Edition: WindowsPE
Architecture: AMD64
Bootable: Yes
Build: 10.0.15063.0 (Windows 10-1703)
Service Pack Level: o
languages: fr-FR (Default)Created: 20/03/2017 02:14:36
Modified: 02/10/2023 17:15:06
So it seems the recovery partion of my C drive is not OK
could it be a problem for ACPHO installation .?
Alemax, what version of Windows are you running? This is telling me your WinRE is Windows 10 version 1703. The wim was created on 20/3/2017. This is about nine iterations back so that just does not seem to be right.
Alemax,
Your WinRE version 1703 is Build 14393 and servicing of that build has ended effective Sept. 12, 2023. Your current installed Windows Build 19041 is version 3448 and is scheduled to end servicing Jan. 12, 2027. Do you recall the date on which you updated to version 3448? Was it after Sept. 12 2023? If it was then it is likely that the update did not service the WinRE on your system due to the fact that it had ended.
This is an issue that I'll bet MS never contemplated. My suggestion for you would to be to download the latest version of Windows 10 from MS and then run the setup.exe file of that installation file while Windows is running. You will get a prompt when you do this asking if you wish to keep all programs and files, answer yes and Windows will perform what is known as an in-place-upgrade of your OS which should upgrade the WinRE along with your current installation of Windows 10 to Version 22H2 Build 19045-3516.
I would think this would fix your issues.
BrunoC wrote:Alemax, what version of Windows are you running? This is telling me your WinRE is Windows 10 version 1703. The wim was created on 20/3/2017. This is about nine iterations back so that just does not seem to be right.
My windows version
Édition Windows 10 Professionnel
Version 22H2
Installé le 05/08/2023
Build du système d’exploitation 19045.3448
Expérience Windows Feature Experience Pack 1000.19044.1000.0
As I wrote, I knew my WINRE version was not OK , but I don't know realy how to correct it
I just see (and answered) the message of Enchantech, , I'll try his solution
Enchantech wrote:Alemax,
Your WinRE version 1703 is Build 14393 and servicing of that build has ended effective Sept. 12, 2023. Your current installed Windows Build 19041 is version 3448 and is scheduled to end servicing Jan. 12, 2027. Do you recall the date on which you updated to version 3448? Was it after Sept. 12 2023? If it was then it is likely that the update did not service the WinRE on your system due to the fact that it had ended.
This is an issue that I'll bet MS never contemplated. My suggestion for you would to be to download the latest version of Windows 10 from MS and then run the setup.exe file of that installation file while Windows is running. You will get a prompt when you do this asking if you wish to keep all programs and files, answer yes and Windows will perform what is known as an in-place-upgrade of your OS which should upgrade the WinRE along with your current installation of Windows 10 to Version 22H2 Build 19045-3516.
I would think this would fix your issues.
OK I will try it
I downloaded MediaCreationTool.exe from the MS site to perform the update, the problem is that after installing my version of windows 10 went to 19045.2965
Édition Windows 10 Professionnel
Version 22H2
Installé le 07/10/2023
Build du système d’exploitation 19045.2965
Expérience Windows Feature Experience Pack 1000.19041.1000.0
The installed version was 19045.3448.
Édition Windows 10 Professionnel
Version 22H2
Installé le 05/08/2023
Build du système d’exploitation 19045.3448
Expérience Windows Feature Experience Pack 1000.19044.1000.0
Under these conditions I don't believe that
the WINRE version may change, so I'm not going to insist on it.
I would think your version should get updated to 19045.3448 under normal Windows Update runs.
You can check your version of WinRE from the System Configuration page of the MVP Assistant in the top pane. The Operating System will tell you the current Windows version (in my case 19045.3324). The Build ID is 19041...
You should see a WinRE line between Boot and BIOS Mode. If you see it there, it will tell you where it is located and the version, which should match the Build ID 19041. In some cases, the WinRE line is not shown. When that has happened, it has been fixed by using reagent to first disable and then enable.
I suggest opening a command prompt and typing
reagentc /?
to see the syntax. Then you may be able to determine what is going on.
Alemax,
Follow Bruno's advice on determining your WinRE version. You should expect to see a match with what your installed version is now ie. 9045.2965
You should run Windows update on the new upgrade so that all released build revisions are downloaded and installed. Doing so should get you back to Revision 3448 This Revision comes via Windows update KB5030211
The latest Revision is 19045 3513 Preview released Sept. 26, 2023
BrunoC wrote:I would think your version should get updated to 19045.3448 under normal Windows Update runs.
That did not work (no changes in WINRE) so I restored my system (acronis backup done before)
You can check your version of WinRE from the System Configuration page of the MVP Assistant in the top pane. The Operating System will tell you the current Windows version (in my case 19045.3324). The Build ID is 19041
...Operating System: Microsoft Windows 10 Professionnel, Version 22H2, Build 10.0.19045.3448, 64-bit
Build ID: 19041.1.amd64fre.vb_release.191206-1406
Installed: 05/08/2023 22:20:57
Last Boot: 09/10/2023 06:45:07
Boot: Disk 4 Partition 1
WinRE: Disk 4 Partition 3 (Build 19041)You should see a WinRE line between Boot and BIOS Mode. If you see it there, it will tell you where it is located and the version, which should match the Build ID 19041. In some cases, the WinRE line is not shown. When that has happened, it has been fixed by using reagent to first disable and then enable.
I suggest opening a command prompt and typing
reagentc /?
to see the syntax. Then you may be able to determine what is going on.
I have just recreated WINPE64 boot media based on WINRE and I do not understand what is happening because it appears:
Wim source: M:\Acronis AUR Media\AUR.XML file contents ACPHO #40729\AUR.wim
Image: Microsoft Windows Recovery Environment (x64)
Build: Windows 10-1703
Languages: fr-FR (Default)
Created: 20/03/2017 02:14:36
Modified: 09/10/2023 10:52:49
One question : is a support based on WINRE is mandatory ?
You probably have two Recovery partitions on your Windows 10 system. This happens when systems undergo a Windows upgrade. The original Windows 10 system had a small Recovery partition at the beginning of the drive. When an upgrade occurs, Microsoft creates a new larger Recovery partition at the end of the drive. The original Recovery partition is left in place at the beginning of the drive. Acronis is finding WinRE in the old partition and using that version. That really shouldn't cause any problem with the Acronis media.
You can confirm whether you have two Recovery partitions by looking at Disk Management. If you see two NTFS partitions in the under 1000 MB size range, you probably have two Recovery partitions. You may see another small partition if your system was built by an OEM. That would be used to reset your computer to the original factory specs.
Here's how to check the status of WinRE on your system. Open a command prompt as administrator and enter the following command:
reagentc /info
This will tell you if WinRE is enabled or disabled. It will also tell you the location of WinRE. You should see a partition number in the location path. It should be at the end of the drive. Report back what you see.
Mustang wrote:You probably have two Recovery partitions on your Windows 10 system. This happens when systems undergo a Windows upgrade. The original Windows 10 system had a small Recovery partition at the beginning of the drive. When an upgrade occurs, Microsoft creates a new larger Recovery partition at the end of the drive. The original Recovery partition is left in place at the beginning of the drive. Acronis is finding WinRE in the old partition and using that version. That really shouldn't cause any problem with the Acronis media.
Even with that wim source ?
Wim source: M:\Acronis AUR Media\AUR.XML file contents ACPHO #40729\AUR.wim
Image: Microsoft Windows Recovery Environment (x64)
Build: Windows 10-1703
You can confirm whether you have two Recovery partitions by looking at Disk Management. If you see two NTFS partitions in the under 1000 MB size range, you probably have two Recovery partitions. You may see another small partition if your system was built by an OEM. That would be used to reset your computer to the original factory specs.
Here's how to check the status of WinRE on your system. Open a command prompt as administrator and enter the following command:
reagentc /info
This will tell you if WinRE is enabled or disabled. It will also tell you the location of WinRE. You should see a partition number in the location path. It should be at the end of the drive. Report back what you see.
Disk partition Link
https://forum.acronis.com/sites/default/files/users/user258451/disk%20C…
_9cefc14982a863ff698537cf2ea1d9cf.png){kind=link}
I can't see two recovery partitions
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) : c11eeded-65a6-11ee-a0aa-34cff6fc2ba4
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.
Maybe I find something
I just used the latest acronis backup of my C drive, right click and choose > Acronis Cyber Protect Home Office > mount, then choose a letter for each partition
Mounting system reserved partitions (L:) and recovery (J:)
The system reserved partition displays
reserved for system (L:)
$WINRE_BACKUP_PARTITION.MARKER 04/21/2017 MARKER file 0KB
The recovery partition displays
local disk (J:)
$WINRE_BACKUP_PARTITION.MARKER 09/26/2023 MARKER file 0KB
Alemax,
Have you manually run Windows Update? Currently your in-place-upgrade is several revisions behind. Those revisions are delivered via Windows Update so you really should do that.
I can see that your System partition at the beginning of the disk is 500 MB. That indicates it's an OEM system and there's a winre.wim contained in that partition. Windows is using partition 3 as the Recovery partition. Acronis media builders are using winre.wim from partition 1. You shouldn't worry. Your system looks fine.
If MVPAssistant can't install ACPHO when you use the AUR wim as the source, it may be due to a problem with the French language in your system. Bruno may be able to help with that. You could always try setting your system language to English US before running MVPAssistant.
Back in January of 2020 I had a weird problem where my disk had two recovery partitions... one for Windows 7 and one for Windows 10. The Acronis media builder was using the wrong one and things did not work well. Thanks to Mustang's help (amongst others), I got to the solution. I think it's the same problem here.
In your case Windows 10 WinRE is on Disk 4, Partition 3. All looks good with respect to the current Windows 10.
Apparently Acronis is using the wrong wim to create the AUR boot media. What you need to do is prevent that from happening. It's not hard.
1. Using Disk Management assign a drive letter to the wrong WinRE partition... the one labeled L: when you mounted the old backup. FYI, using the System Configuration of the MVP Assistant you can see how each partition of your disk is defined. It looks like this is Disk 4, Partition 1.
2. Change the name of the winre.wim file (e.g. old_winre.wim). If you cannot change the name, you may need to take ownership of the folder.
3. Unassign the drive letter for the old partition.
At that point you should be in good shape to rebuild the AUR media and it should find the correct wim.
Here's my old forum topic...
I see your post about the Marker files. We don't know exactly how Acronis searches for winre.wim. It would be interesting to see if just deleting the Marker file from your L: partition 1 would stop Acronis from using that winre.wim.
BrunoC wrote:Back in January of 2020 I had a weird problem where my disk had two recovery partitions... one for Windows 7 and one for Windows 10. The Acronis media builder was using the wrong one and things did not work well. Thanks to Mustang's help (amongst others), I got to the solution. I think it's the same problem here.
In your case Windows 10 WinRE is on Disk 4, Partition 3. All looks good with respect to the current Windows 10.
Apparently Acronis is using the wrong wim to create the AUR boot media. What you need to do is prevent that from happening. It's not hard.
1. Using Disk Management assign a drive letter to the wrong WinRE partition... the one labeled L: when you mounted the old backup. FYI, using the System Configuration of the MVP Assistant you can see how each partition of your disk is defined. It looks like this is Disk 4, Partition 1.
A problem here the partition on L: is defined as system reserved partition (not a Winre partition)
and there's no wim.
From the disk management I assign a drive letter and a folder for mounting the contents which is
$WINRE_BACKUP_PARTITION.MARKER 04/21/2017 MARKER file 0KB
I changed the name but after the rebuild of AUR, the result gives not the correct .WIM
2. Change the name of the winre.wim file (e.g. old_winre.wim). If you cannot change the name, you may need to take ownership of the folder.
3. Unassign the drive letter for the old partition.
At that point you should be in good shape to rebuild the AUR media and it should find the correct wim.
Here's my old forum topic...
Did you set Explorer to view all hidden and system files. I'm sure there must be a wim there.
BrunoC wrote:Did you set Explorer to view all hidden and system files. I'm sure there must be a wim there.
Yes, I did but as the file size is zero I don't know what I can do
You are looking for a file named winre.wim not the marker file. You will find it at your L:\Recovery\WinRE\winre.wim. Open a command prompt as administrator and enter the following commands:
L:
cd \Recovery\WinRE (The prompt should change to L:\Recovery\WinRE>)
attrib -s -h winre.wim (You should see no message.)
ren winre.wim Xwinre.wim (You should see no message.)
dir (You should see a file named Xwinre.wim listed.)
That should stop the Acronis Media Builder from finding it and force it to find the correct winre.wim in the Recovery partition.
Mustang wrote:You are looking for a file named winre.wim not the marker file. You will find it at your L:\Recovery\WinRE\winre.wim. Open a command prompt as administrator and enter the following commands:
I used Management console to attrib letter L: to the reserved partition of disk 4 partition 1
picture link
https://forum.acronis.com/sites/default/files/users/user258451/disk%20C…
Then I start to enter commands
L:
copy of the command prompt (mode administrator)
L:\>dir
Le volume dans le lecteur L s’appelle Réservé au système
Le numéro de série du volume est FAF6-7CC9Répertoire de L:\
21/04/2017 11:54 0 $WINRE_BACKUP_PARTITION.MARKER
1 fichier(s) 0 octets
0 Rép(s) 106 070 016 octets libresL:\>cd \Recovery\WinRE
Le chemin d’accès spécifié est introuvable.L:\>
Did i make some mistake , forget something ?
Some tries
I see above you suggested to delete the file $WINRE_BACKUP_PARTITION.MARKER
I tried that and create a new support based on Winre ,
but the result did not changeI tried too to erase the partition (fill with 0) but once more the result did not change
end to tries
cd \Recovery\WinRE (The prompt should change to L:\Recovery\WinRE>)
attrib -s -h winre.wim (You should see no message.)
ren winre.wim Xwinre.wim (You should see no message.)
dir (You should see a file named Xwinre.wim listed.)
That should stop the Acronis Media Builder from finding it and force it to find the correct winre.wim in the Recovery partition.
Does C:\Windows\System32\Recovery contain a winre.wim file?
BrunoC wrote:Does C:\Windows\System32\Recovery contain a winre.wim file?
No, only this reagent.xml
<?xml version='1.0' encoding='utf-8' standalone='yes'?>
<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>
I made a mistake in the folder name. Try this instead:
L:
cd \Recovery\WindowsRE (The prompt should change to L:\Recovery\WinRE>)
attrib -s -h winre.wim (You should see no message.)
ren winre.wim Xwinre.wim (You should see no message.)
dir (You should see a file named Xwinre.wim listed.)
Notice the cd command should be WindowsRE not WinRE. The problem here is that all the folders and files are hidden so they don't show in with the dir command until the hidden attribute is removed.
Mustang wrote:I made a mistake in the folder name. Try this instead:
L:
cd \Recovery\WindowsRE (The prompt should change to L:\Recovery\WinRE>)
attrib -s -h winre.wim (You should see no message.)
ren winre.wim Xwinre.wim (You should see no message.)
dir (You should see a file named Xwinre.wim listed.)
Notice the cd command should be WindowsRE not WinRE. The problem here is that all the folders and files are hidden so they don't show in with the dir command until the hidden attribute is removed.
Seems to work here after the result
C:\WINDOWS\system32>L:
L:\>cd \Recovery\WindowsRE
L:\Recovery\WindowsRE>
L:\Recovery\WindowsRE>attrib -s -h winre.wim
L:\Recovery\WindowsRE>ren winre.wim Xwinre.wim
L:\Recovery\WindowsRE>dir
Le volume dans le lecteur L s’appelle Réservé au système
Le numéro de série du volume est FAF6-7CC9
Répertoire de L:\Recovery\WindowsRE
21/04/2017 12:00 378 531 476 Xwinre.wim
1 fichier(s) 378 531 476 octets
0 Rép(s) 106 070 016 octets libres
L:\Recovery\WindowsRE>
I will now create a new support based on Winre and give you the result
Thanks a lot for your help
Result is still bad
Wim source: M:\Acronis AUR Media\AUR.XML file contents ACPHO #40729\AUR.wim
Image: Microsoft Windows Recovery Environment (x64)
Build: Windows 10-1703
I don't understand , I have checked the folder
L:\>cd \Recovery\WindowsRE
L:\Recovery\WindowsRE>dir
Le volume dans le lecteur L s’appelle Réservé au système
Le numéro de série du volume est FAF6-7CC9
Répertoire de L:\Recovery\WindowsRE
21/04/2017 12:00 378 531 476 Xwinre.wim
1 fichier(s) 378 531 476 octets
0 Rép(s) 106 070 016 octets libres
Seems OK
That is surprising. Let's take a look at winre.wim in your Recovery partition. Start a new project using MVPAssistant and select WinRE as the source (not the AUR.wim). What do you see for the build of the image? Is it still 10-1703?
Did you run AUR media builder again after changing the name of the bad wim file? You don't mention that.
BrunoC wrote:did you run AUR media builder again after changng the name of the bad wim file? You don't mention that.
Yes,
It seems you missed what I wrote in my responses to Mustang
"I will now create a new support based on Winre and give you the result"
Mustang wrote:That is surprising. Let's take a look at winre.wim in your Recovery partition. Start a new project using MVPAssistant and select WinRE as the source (not the AUR.wim). What do you see for the build of the image? Is it still 10-1703?
The result
Source File: winre.wim
Type: Wim
Name: Microsoft Windows Recovery Environment (x64)
Index: 1
Edition: WindowsPE
Architecture: AMD64
Bootable: Yes
Build: 10.0.19041.1 (Windows 10-2004)
Service Pack Level: 0
Languages: fr-FR (Default)
Created: 07/12/2019 15:44:12
Modified: 05/08/2023 22:10:54
Other Tries
Using your informations about changing name of L:\Recovery\WindowsRE :
I changed the Xwinre.wim name this way
L:\Recovery\WindowsRE>dir
Le volume dans le lecteur L s’appelle Réservé au système
Le numéro de série du volume est FAF6-7CC9
Répertoire de L:\Recovery\WindowsRE
21/04/2017 12:00 378 531 476 XWinre.Wim.old
1 fichier(s) 378 531 476 octets
0 Rép(s) 106 065 920 octets libres
L:\Recovery\WindowsRE>
And then use create a new AUR.WIM using Acronis Universal restore Bootable media Builder
The the result is still the bad result
END of TRIES
It just seems that Acronis bootable media builder is able to recover non existing file(s) !
I don't think Acronis is able to use the old winre.wim that you have successfully renamed. My best guess is they have stored the old wim file somewhere on your computer so they can use it again later. I'll do some experimenting on my system to try and figure out how to get the Acronis Media builder to use the correct winre.wim from your Recovery partition.
In the meantime, you can prove they can't recover the renamed wim by deleting it. It's of no value to you and it won't cause any harm to delete it. You can use this command to delete it after you change the directory:
del Winre.Wim.old
Mustang wrote:I don't think Acronis is able to use the old winre.wim that you have successfully renamed. My best guess is they have stored the old wim file somewhere on your computer so they can use it again later. I'll do some experimenting on my system to try and figure out how to get the Acronis Media builder to use the correct winre.wim from your Recovery partition.
In the meantime, you can prove they can't recover the renamed wim by deleting it. It's of no value to you and it won't cause any harm to delete it. You can use this command to delete it after you change the directory:
del Winre.Wim.old
I already have done these kind of tries (answer to your message of10/10/2023) I reproduce here after
Some tries
I see above you suggested to delete the file $WINRE_BACKUP_PARTITION.MARKER
I tried that and create a new support based on Winre ,
but the result did not change
I tried too to erase the partition (fill with 0) but once more the result did not change
end to tries
I renamed winre.wim on my system. Then I ran the AUR media builder. It told me the files for creating media based on winre were missing and the WinRE option was grayed out.
Let's see if we can find where the AUR media builder is finding the old winre.wim on you computer. Use the Windows File Manager and highlight C:\. Then enter winre.wim in the search box in the upper right corner. If nothing is found, try searching all other drive letters for winre.wim. You can also search your C: for any wim files by entering *.wim in the search box. You will see a lot of normal Windows wim files. See if the result shows anything the might be the old winre.wim file.
Alemax wrote:BrunoC wrote:Does C:\Windows\System32\Recovery contain a winre.wim file?
No, only this reagent.xml
<?xml version='1.0' encoding='utf-8' standalone='yes'?>
<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 reagent.xml file does not look good. It is not filled in with anything.
You say there is no winre.wim in the Recovery folder, but are you viewing hidden and system files to be sure. Given what I see in the reagent.xml file, I wonder how the MVP Assistant found the correct wim since it either uses the xml file or looks in the Recovery folder. I may be wrong in assuming you have created a new project in the MVP Assistant and chosen WinRE.
Have you tried to run
reagentc /disable
reagentc /enable
The /disable should bring in the winre.wim from the correct partition and place it in C:\Windows\System32\Recovery. The /enable should put it back in the proper recovery partition and fix things up.
As with Mustang, I am at a loss as to understand why the AUR build would find the old winre.wim if you have changed the name of it.
Mustang wrote:I renamed winre.wim on my system. Then I ran the AUR media builder. It told me the files for creating media based on winre were missing and the WinRE option was grayed out.
Let's see if we can find where the AUR media builder is finding the old winre.wim on you computer. Use the Windows File Manager and highlight C:\. Then enter winre.wim in the search box in the upper right corner. If nothing is found, try searching all other drive letters for winre.wim. You can also search your C: for any wim files by entering *.wim in the search box. You will see a lot of normal Windows wim files. See if the result shows anything the might be the old winre.wim file.
I am used to use EveryThing for searching files and I find some winre.wim files two of my others system disk E: and F: whith the same partitions as my drive C
Both where located in the E:\$WinREAgent folder backup
where is a file named location
File location contents
[WinRE Location]
Partition offset=255484493824
Relative path=\Recovery\WindowsRE
OS Guid={00787D94-31D9-11EE-953D-34CFF6FC2BA0}
In E:\$WinREAgent is also a folder Rollback
which contents two files
Rollback.xml
<RollbackHelper><Checkpoint Value="0"/><Checkpoint Value="4"/><Checkpoint Value="5"/></RollbackHelper>
RollbackInfo.ini
[GeneralInfo]
CopiedWimPath=C:\$WinREAgent\Scratch\update.wim
ExportedWimPath=C:\$WinREAgent\Scratch\exported.wim
BackupWimPath=C:\$WinREAgent\Backup\WinRE.wim
[BackupWimPath]
NewWinREHash=nztwtyBwm6h5SH6+gf8VqugbPtw5p9KvXHAK9dDBnag=
[ExecutionInfo]
CommitStart=Yes
CommitComplete=Yes
End of $WinREAgent
Thinks
As i don't find such a winre.wim on my C drive i think i could test the AUR media builder after disconnectinq the 2 other system drive E: and F:
I never think such files could be searched on other drive than the current system drive
Alemax wrote:I am used to use EveryThing for searching files and I find some winre.wim files two of my others system disk E: and F: whith the same partitions as my drive C
Why do you have two other online drives with the same partitions as C: drive. I think this may be dangerous.
Okay, that explains it. The AUR media builder should find the correct winre.wim after you disconnect the other systems.
BrunoC wrote:Alemax wrote:I am used to use EveryThing for searching files and I find some winre.wim files two of my others system disk E: and F: whith the same partitions as my drive C
Why do you have two other online drives with the same partitions as C: drive. I think this may be dangerous.
Partition structures are the same, and excepted partition 1 (windows 7 to W10 migration) the contents are different.
What could be dangerous ?
until now I never had problem whith that
Mustang wrote:Okay, that explains it. The AUR media builder should find the correct winre.wim after you disconnect the other systems.
The result for AUR.WIM is OK
Wim source: M:\Acronis AUR Media\AUR.XML file contents ACPHO #40729\AUR.wim
Image: Microsoft Windows Recovery Environment (x64)
Build: Windows 10-2004
Languages: fr-FR (Default)
Created: 07/12/2019 15:44:12
Modified: 12/10/2023 07:49:06
but when booting from rescue media stick (build USB Drive) I got an error (may some driver is missing)
He after some links to the snapshots I have done
ACPHO error
https://forum.acronis.com/sites/default/files/users/user258451/Presse-p…
Launch bar displayed
(there 2 irfanview icones ,it's easiest to access the program)
https://forum.acronis.com/sites/default/files/users/user258451/Presse-p…
AUR
https://forum.acronis.com/sites/default/files/users/user258451/Presse-p…
Next
The ACPHO error (I used the error code for searching by Acronis, but Acronis found nothing)
Have you an idea about the possibility to remove definitly the E:\$WinREAgent and so on ?
I'm glad to see you now have the correct Windows 10 winre.wim being used in the AUR recovery media.
The error you're getting with ACPHO means the program isn't happy with an Acronis file named snapapi.dll found in X:\Windows\System32. It works in conjunction with the snapman.sys driver found in X:\Windows\System32\Drivers. You can correct this error by following the steps below:
1. Create a new project with MVPAssistant using WinRE (not the AUR.wim) as the source. Follow it to completion and boot the media. If ACPHO runs properly, go to step 2. If you get the same error, stop and report back here.
2. Open the new project with MVPAssistant in Advanced mode. Mount the image. With the image mounted click on Explore in the Image menu. Navigate to \Windows\System32 and scroll down to snapapi.dll. Hover the mouse over the file and write down the version number. I see 4.8.0.4057. Copy the file to a location on your hard drive. Now navigate to \Windows\System32\Drivers and scroll down to snapman.sys. Write down the version number. Copy the file to the same location on your hard drive. Unmount the image and close the project.
3. Open your AUR project that has the ACPHO error. Mount the image and click the Image/Explore menu item. Replace \Windows\System32\snapapi.dll with the version you saved to your hard drive. Replace \Windows\System32\Drivers\snapman.sys with the version you saved to your hard drive. Unmount the image and build the media. Boot the media and see if both ACPHO and Universal Restore work properly.
Now let's talk about the disks in your computer. You seem to have 3 Windows system disks. One with Windows 7 and two with Windows 10. Are you booting from all of these disks? If so, how do you do it? Do you enter the BIOS and select the disk you want to boot from? What type of disks are they (HDD, SSD, NVMe)? These are a lot of question, but there're all important.
Booting Windows 7 and Windows 10 systems that are able to see each other and the same data disks is dangerous. How often do you see your drives need to be scanned for errors? Do you run into permissions problem on your disks?
I take it your motherboard isn't very new. Modern motherboards don't like seeing multiple Windows systems. The BIOS can start to make changes to the BCD boot files and cause systems to fail to boot.
I used to have multiple systems in a single computer, but have stopped that practice. I now have my Windows systems on that computer on 2.5" SSD's. This allows me to use a swappable drive tray system so I can select which system to boot by swapping the disks. I don't use M.2 NVMe disks on this computer because they are to hard to swap.