-
- Expert
- Posts: 133
- Liked: 1 time
- Joined: Dec 15, 2015 1:07 pm
- Contact:
Canot create recovery media on multi boot systems
Hi,
we have several multi boot systems with parallel Windows installations, e.g. one Windows 7 64-bit and one Windows 7 32-bit.
Currently we are not able to create Veeam reocvery medias on that Workstations. The following messages are in the log window:
- Failed: Mounting Recovery Environment Image (00:21)
- Success: Unmounting recovy image (00:02)
- Warning: Failed to delete recovery media's temporary files from C:\Users\%username%\AppData\Local\Temp\yij1g5zh.4mz. Unmount the Image, and try deleting files manually
- Success: Unmounting recovery image (00:02)
- Warning: Failed to delete recovery media's temporary files from C:\Users\%username%\AppData\Local\Temp\dfmrfc42.b30. Unmount the Image, and try deleting files manually
- Success: Unmounting recovery image (00:02)
- Warning: Failed to delete recovery media's temporary files from C:\Users\%username%\AppData\Local\Temp\ewjjrkr.epz. Unmount the Image, and try deleting files manually
- Failed: Failed to create recovery media: Access denied
After that another window opens:
- Title: "Windows Component Missing"
- Text: Windows Recovery Environment (WinRE) component is missing. Specify the location of Microsoft Windows 7 Enterprise x64 installation files (you may need to insert your Windows Installation media). Alternatively, download and install Windows ADK.
We have that problem on all multi boot systems. The user is in the local Administrators group.
What can we do to use Endpoint Backup on those systems?
Regards,
UT2015
we have several multi boot systems with parallel Windows installations, e.g. one Windows 7 64-bit and one Windows 7 32-bit.
Currently we are not able to create Veeam reocvery medias on that Workstations. The following messages are in the log window:
- Failed: Mounting Recovery Environment Image (00:21)
- Success: Unmounting recovy image (00:02)
- Warning: Failed to delete recovery media's temporary files from C:\Users\%username%\AppData\Local\Temp\yij1g5zh.4mz. Unmount the Image, and try deleting files manually
- Success: Unmounting recovery image (00:02)
- Warning: Failed to delete recovery media's temporary files from C:\Users\%username%\AppData\Local\Temp\dfmrfc42.b30. Unmount the Image, and try deleting files manually
- Success: Unmounting recovery image (00:02)
- Warning: Failed to delete recovery media's temporary files from C:\Users\%username%\AppData\Local\Temp\ewjjrkr.epz. Unmount the Image, and try deleting files manually
- Failed: Failed to create recovery media: Access denied
After that another window opens:
- Title: "Windows Component Missing"
- Text: Windows Recovery Environment (WinRE) component is missing. Specify the location of Microsoft Windows 7 Enterprise x64 installation files (you may need to insert your Windows Installation media). Alternatively, download and install Windows ADK.
We have that problem on all multi boot systems. The user is in the local Administrators group.
What can we do to use Endpoint Backup on those systems?
Regards,
UT2015
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Canot create recovery media on multi boot systems
Hi UT2015,
Quick question... What service pack are you running on those machines?
Mike
Quick question... What service pack are you running on those machines?
Mike
-
- Expert
- Posts: 133
- Liked: 1 time
- Joined: Dec 15, 2015 1:07 pm
- Contact:
Re: Canot create recovery media on multi boot systems
Windows 7 SP1 and all the latest Windows Updates integrated
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Canot create recovery media on multi boot systems
Hi,
I talked to some people and they believe that it is best to create a support case. I heard about this already a few times but it appears to be a different reason on a case-by-case so please create the case through the VEB UI, post the case ID here and if you have a solution, please let us know that here also
Many thanks
Mike
I talked to some people and they believe that it is best to create a support case. I heard about this already a few times but it appears to be a different reason on a case-by-case so please create the case through the VEB UI, post the case ID here and if you have a solution, please let us know that here also
Many thanks
Mike
-
- Enthusiast
- Posts: 45
- Liked: 15 times
- Joined: Jan 03, 2017 5:25 pm
Re: Canot create recovery media on multi boot systems
Hello,
UT2015 did you manage to solve the problem? I've came across the same issue
UT2015 did you manage to solve the problem? I've came across the same issue
-
- Product Manager
- Posts: 14722
- Liked: 1705 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
-
- Expert
- Posts: 133
- Liked: 1 time
- Joined: Dec 15, 2015 1:07 pm
- Contact:
Re: Canot create recovery media on multi boot systems
Hi stvajnkf,
no, we did not manage to solve the problem.
Because of other severe bugs in Endpoint Backup (see veeam-agent-for-windows-f33/failed-to-b ... 38-15.html), we are not using Veeam Endpoint anymore to backup our clients.
Best regards,
UT2015
no, we did not manage to solve the problem.
Because of other severe bugs in Endpoint Backup (see veeam-agent-for-windows-f33/failed-to-b ... 38-15.html), we are not using Veeam Endpoint anymore to backup our clients.
Best regards,
UT2015
-
- Expert
- Posts: 194
- Liked: 18 times
- Joined: Apr 16, 2015 9:01 am
- Location: Germany / Bulgaria
- Contact:
Re: Canot create recovery media on multi boot systems
Had the same issue, looks like for some reason on C:\users\myuser\appdata\local\temp permissions were not set at all, not sure why or which software caused that. Forcing the permissions from C:\users\myuser\appdata\local to subfolders seems to have solved the issue.
-
- Expert
- Posts: 133
- Liked: 1 time
- Joined: Dec 15, 2015 1:07 pm
- Contact:
Re: Canot create recovery media on multi boot systems
I actually did check the permissions on temp folder that time, because the log said that some files in temp folder could not be accessed. The permissions were actually correct.
Because it is in our opinion not reliable enough we stopped using Veeam Endpoint/Agent for Windows, therefore I cannot tell you if it would work now.
Because it is in our opinion not reliable enough we stopped using Veeam Endpoint/Agent for Windows, therefore I cannot tell you if it would work now.
Who is online
Users browsing this forum: Bing [Bot], neo24382 and 22 guests