(Solved) Missing Original ATIH WinPE.zip files (MVP_ATIPEBuilder)
-> Windows 10 x64 Version 1709 (Build 16299.19) german
-> TrueImage 2018 b9850
-> DiskDirector 12 b3297
When trying to build a custom PE environment using the MVP Tool v1.21 I get the following error:
=================================================================
------------------------------
[Mounting amd64 winpe.wim file.]
------------------------------
Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.16299.15
Fehler: 3
Das System kann den angegebenen Pfad nicht finden.
Die DISM-Protokolldatei befindet sich unter "C:\WINDOWS\Logs\DISM\dism.log".
=================================================================
Analyzing the error I found that the "Original ATIH WinPE.zip files" for TrueImage and DiskDirector are missing. Only the files for UniversalRestore are in place.
Using the repair option in TrueImage and DiskDirector did not help.
Any advice how to generate the missing files?
TIA
Another thing that would help would be for you to upload the log from the MVPTool.
Thank for your response.
After reading I looked a little deeper into dism.log and there were error messages and so decided to try a clean run. I did a cleanup of mountpoints with dism and cleaned the %tmp% directory. After a reboot I ran the build procedure with admin rights.
In area [Saving changes to amd64 winpe.wim file.] of the build log an error message shows up:
---------------------------------------
[Saving changes to amd64 winpe.wim file.]
---------------------------------------
Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.16299.15
Abbilddatei: C:\Users\Install\AppData\Local\Temp\MBM-VOU-PBS-WBT-IOA-N3N-PCG-EO\PE\media\sources\boot.wim
Abbildindex: 1
Fehler: 32
Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.
Die DISM-Protokolldatei befindet sich unter "C:\WINDOWS\Logs\DISM\dism.log".
I have no idea which other process puts a lock onto boot.wim. An excerpt from dism.log is in dism_err.log.
Booting the iso from this build there is a command window with only 2 lines:
X:\windows\system32>wpeinit
X:\windows\system32
waiting for input: No attempt to start TrueImage.
Attached from boot: winpeinit.log and winpeshl.log
Attached from build part of dism.log: dism_err.log
Hoping you have an idea.
Sorry about the filenames:
| 430023-139951.log | <-- winpeinit.log |
| 430023-139953.log | <--- winpeshl.log |
| 430023-139956.log | <-- dism_err.log |
AcroBS, the log file that Paul was asking for is the one found in the C:\MVP_ATIPEBuilder_v121\Logs folder that is created when you run the script.
Hello Steve, thank you clarification.
This is the file:
Sorry that was the wrong file. This should be the correct one.
PS
I do not know who or what does this obscure naming. The name of the file is MVP_ATIPEBuilder_05-11-2017_23.47.10.log
Thanks for the tool log.
The first suggestion would be to move your script source from H:\Software\Acronis\ATIH\MVP Tools\MVP_ATIPEBuilder_v121 to be in C:\MVP_ATIPEBuilder_v121 and then run it again to see if the initial errors shown no longer are given.
The current log shows:
------------------- ACRONIS INFORMATION: ------------------- ATIH VERSION: NotFound ATIH BUILD: NotFound ---------------- ADK INFORMATION: ---------------- Installed: NotFound WINRE64: NotFound WINRE86: NotFound
I have just run the script on one of my computers (with ATI 2017) and my log looks as below: (for comparison).
------------------- ACRONIS INFORMATION: ------------------- ATIH VERSION: 2017 ATIH BUILD: 20.0.0.8058 UR VERSION: 11.5.0.40010 DD VERSION: NotFound DD BUILD: NotFound Acronis Revive VERSION: NotFound Acronis Revive BUILD: -------------- VARIABLE PATHS: -------------- SCRIPT SOURCE: C:\MVP_ATIPEBuilder_v121 ATIH PATH: C:\Program Files (x86)\Acronis\TrueImageHome\WinPE UR PATH: C:\Program Files (x86)\Acronis\UniversalRestore\WinPE DD12 PATH: NotFound Acronis Revive PATH: NotFound ADK PATH: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment ---------------- ADK INFORMATION: ---------------- Installed: 10.0.10586 WINRE64: NotFound WINRE86: NotFound @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ MVP ATIPeBuilder LOG DETAILS: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 07-11-2017 15.28.40 You chose [2.] "64-bit Media Builder" - USER selected. 07-11-2017 15.28.40 Skipping network share mapping - USER selected. 07-11-2017 15.28.40 Mounting amd64 winpe.wim. 07-11-2017 15.28.40 Leaving the WinPE default language as English - USER selected. 07-11-2017 15.28.40 True Image Found. Adding It. 07-11-2017 15.28.40 Universal Restore Found. Adding It. 07-11-2017 15.28.40 Disk Director 12 Not Found. Skipping It. 07-11-2017 15.28.40 Acronis Revive 2017 Not Found. Skipping It. 07-11-2017 15.28.40 Adding in extra goodies. 07-11-2017 15.28.40 Skipping Double Driver local system 64-bit driver injection - USER selected. 07-11-2017 15.28.40 Skipping custom 64-bit driver injection - USER selected. 07-11-2017 15.28.40 Skipping MSiScsi Support Packages - USER selected. 07-11-2017 15.28.40 Skipping Bitlocker Support Packages - USER selected. 07-11-2017 15.28.40 Do not prompt for any key at boot - USER selected. 07-11-2017 15.28.40 Skipping WinPE screen resolution - USER selected. 07-11-2017 15.28.40 Saving changes to amd64 winpe.wim file. 07-11-2017 15.28.40 Creating Acronis_amd64.iso. 07-11-2017 15.28.40 Acronis_amd64.iso is located in "C:\MVP_ATIPEBuilder_v121\ISO" 07-11-2017 15.28.40 Creating Acronis_amd64.wim. 07-11-2017 15.28.40 Acronis_amd64.wim is located in "C:\MVP_ATIPEBuilder_v121\ISO\Wim". 07-11-2017 15.28.40 Skipping bootable USB flash drive creation - USER Selected. 07-11-2017 15.28.40 Skipping CD/DVD burning - USER Selected. 07-11-2017 15.28.40 Cleaning up now. 07-11-2017 15.28.40 FINISHED.
The key elements of the script execution as shown immediately above look to be very similar to that of your log, i.e.
05-11-2017 23.47.10 Acronis_amd64.iso is located in "H:\Software\Acronis\ATIH\MVP Tools\MVP_ATIPEBuilder_v121\ISO" 05-11-2017 23.47.10 Creating Acronis_amd64.wim. 05-11-2017 23.47.10 Acronis_amd64.wim is located in "H:\Software\Acronis\ATIH\MVP Tools\MVP_ATIPEBuilder_v121\ISO\Wim".
So the tool created both the ISO and WIM files in the folder shown, as it should.
Hello Steve
thank you for your time. I followed your advice and move the whole procedure to drive c:. Here is the new log file:
------------------- ACRONIS INFORMATION: ------------------- ATIH VERSION: NotFound ATIH BUILD: NotFound UR VERSION: NotFound DD VERSION: NotFound DD BUILD: NotFound Acronis Revive VERSION: NotFound Acronis Revive BUILD: NotFound -------------- VARIABLE PATHS: -------------- SCRIPT SOURCE: C:\MVP_ATIPEBuilder_v121 ATIH PATH: C:\Program Files (x86)\Acronis\TrueImageHome\WinPE UR PATH: C:\Program Files (x86)\Acronis\UniversalRestore\WinPE DD12 PATH: C:\Program Files (x86)\Common Files\Acronis\DiskDirector\WinPE Acronis Revive PATH: NotFound ADK PATH: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment ---------------- ADK INFORMATION: ---------------- Installed: NotFound WINRE64: NotFound WINRE86: NotFound @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ MVP ATIPeBuilder LOG DETAILS: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 07-11-2017 17.37.11 You chose [2.] "64-bit Media Builder" - USER selected. 07-11-2017 17.37.11 Skipping network share mapping - USER selected. 07-11-2017 17.37.11 Mounting amd64 winpe.wim. 07-11-2017 17.37.11 Leaving the WinPE default language as English - USER selected. 07-11-2017 17.37.11 True Image Found. Adding It. 07-11-2017 17.37.11 Universal Restore Found. Adding It. 07-11-2017 17.37.11 Disk Director 12 Found. Adding It. 07-11-2017 17.37.11 Acronis Revive 2017 Not Found. Skipping It. 07-11-2017 17.37.11 Adding in extra goodies. 07-11-2017 17.37.11 Skipping Double Driver local system 64-bit driver injection - USER selected. 07-11-2017 17.37.11 Skipping custom 64-bit driver injection - USER selected. 07-11-2017 17.37.11 Skipping MSiScsi Support Packages - USER selected. 07-11-2017 17.37.11 Skipping Bitlocker Support Packages - USER selected. 07-11-2017 17.37.11 Do not prompt for any key at boot - USER selected. 07-11-2017 17.37.11 Skipping WinPE screen resolution - USER selected. 07-11-2017 17.37.11 Saving changes to amd64 winpe.wim file. 07-11-2017 17.37.11 Creating Acronis_amd64.iso. 07-11-2017 17.37.11 Acronis_amd64.iso is located in "C:\MVP_ATIPEBuilder_v121\ISO" 07-11-2017 17.37.11 Creating Acronis_amd64.wim. 07-11-2017 17.37.11 Acronis_amd64.wim is located in "C:\MVP_ATIPEBuilder_v121\ISO\Wim". 07-11-2017 17.37.11 Skipping bootable USB flash drive creation - USER Selected. 07-11-2017 17.37.11 Skipping CD/DVD burning - USER Selected. 07-11-2017 17.37.11 Cleaning up now. 07-11-2017 17.37.11 FINISHED.
There are differrences to your log:
1. In section ACRONIS INFORMATION no version and build information is found.
2. In section ADK INFORMATION the version info is missing too.
And there is an error display in the screen log of the MVP_ATIPEBuilder_v121 procedure:
=================================================================
---------------------------------------
[Saving changes to amd64 winpe.wim file.]
---------------------------------------
Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.16299.15
Abbilddatei: C:\Users\Install\AppData\Local\Temp\MBM-VOU-PBS-WBT-IOA-N3N-PCG-EO\PE\media\sources\boot.wim
Abbildindex: 1
Fehler: 32
Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.
Die DISM-Protokolldatei befindet sich unter "C:\WINDOWS\Logs\DISM\dism.log".
=================================================================The other messages are looking normal.
Do you have an idea how to explore the differences and the error message?
TIA
I am not the expert on DISM issues - we may need to wait for Paul (Mustang) to see the updates and give us the benefit of his expertise in this area.
You could try doing a Dism /Cleanup-Mountpoints to see if this will cleanup any problems that are potentially locking out the script from saving the modified WIM file?
See webpage: DISM Image Management Command-Line Options
En réponse à I am not the expert on DISM… par truwrikodrorow…
Hello Steve,
I executed the /Clenaup-Mountpoint command already before the last logged run.
But perhaps you can help me a little further. Because I do not know the source of the program can you tell me where the program looks for the installed versions (in the registry?) of the Acronis programs, since these versions are not displayed in my log file. Bychance I may find something.
TIA
Please see your Account > Messages.
I already told you where to look in the registry. Please read my previous post and answer the questions I asked.
En réponse à I already told you where to… par truwrikodrorow…
Hello Paul,
after a hint from Steve I posted the log file in reply #9.
The missing answer to
HKLM\SOFTWARE\WOW6432Node\Acronis\TrueImageHome\Settings\WinPEResources is
C:\Program Files (x86)\Acronis\TrueImageHome\WinPE\winpe_resources.dll.
I was puzzled because the file !!!!README!!!!_Run_as_ADMIN!!!.txt mentions locations of WinPE.zip files, which I do not find on my system. Therefore the title which now obvoiously is no more accurate.
I think the critical point of my problem is in the realm of the dism command. The error message is not found in questioned log file but only in the real time window. This is shown at the end of entry #9.
I add an excerpt of the windows directory dism.log reflecting the time section in entry #9.
Thank you.
Looks to me like the MVPTool is working on your system. The only issue is that the routine used to find the Acronis version numbers isn't working on a German system. The log show that True Image, DD12 and UR have been found ans are added to the build. If you are getting a dism error, the problem may be with the ADK. Please try a test.
First create two folders at C:\mount and C:\Temp. Copy winpe.wim from C:\Program Files(x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us to C:\Temp. Then rename C:\Temp\winpe.wim to C:\Temp\boot.wim. Go to the Windows start menu at Windows Kits and run Deployment and Imaging Tool Environment as administrator. Enter the following line:
dism /Mount-Wim /WimFile:C:\Temp\boot.wim /Index:1 /MountDir:C:\mount
Go to C:\mount\Program Files and create a new folder called Acronis. Then copy a few small files to the Acronis folder. It doesn't matter what files you use. This is only a test to see if dism is working on your system.
Enter the following line in the open command window:
dism /Unmount-Wim /MountDir:C:\mount /commit
Does this command complete successfully? If not, I think you will need to reinstall the ADK.
En réponse à Looks to me like the MVPTool… par truwrikodrorow…
Hello Paul,
finally I found the source of the error. But in sequence:
First I checked if there whether the used environment was clear. When not there had to be taken extra steps (see below).
Doing input one by into the command window the subdirectory Acronis was successfully integrated into boot.wim.
Putting the commands into a procedure und running it: the result was successfull too.
The next step was to reinstall the ADK. Your test sequence ran successfully again.
But running MVP_ATIPEBuilder.exe gave the error and nothing was integrated into boot.wim. At the end of the program there was still a wim image mounted and none of the /cleanup-... switches cleared the error - the image remained mounted with status invalid. The reason for this was that not all files in the subdirectories below the mountpoint were deleted. Using handle from sysinternals showed that the system process (pid 4) hold locks these files. Only a reboot cleared the locks and the dism /unmount-wim /mountdir:<mountdir> /discard unmounted the wim image successfully and cleared the dism environment.
I have done a PM with detailed steps of my investigation.
The next step would be integrating step by step the dism commands of your program into a procedure and watch which wim file raises the error. This I cannot do without your help. But perhaps you find another way to investigate the reason for the error on my system.
Thank you for your time.
I looked at your message. I think the problem in related to your system TEMP folder. Maybe a permissions problem. It seems strange that your TEMP folder is located in an Install folder rather than an AppData folder. Try making a temporary change to the TEMP environment variable before running the MVPTool.
Make sure C:\Temp exists then follow these steps:
1. Open Control Panel and select System.
2. Click on Advanced System Settings.
3. Click the Environment Variables button.
4. Highlight TEMP.
5. Write down the exact path shown in Variable value. (You can change back to this value after running the MVPTool.)
6. Change the value to C:\Temp and save the changes.
Make sure the mount points are clear and try running the MVPTool. You can change the TEMP location back now.
En réponse à I looked at your message. I… par truwrikodrorow…
I took the steps you suggested. First I changed only the TEMP variable. With this the build procedure missed some files right in the beginning. So I interrupted this run.
Then I changed the variable TMP also to c:\temp. Afterwards the build procedure ran to the end but raised the same error as before when working with dism.
So the test gve no further clues.
A log of my investigation is in another PM.
Sorry, I have no idea what the problem is.
One suggestion to offer here: try creating a new user account (Administrator) then retry running the MVP Custom ATIPE script again.
En réponse à One suggestion to offer here… par truwrikodrorow…
Hello Steve,
I followed your proposal and the build was successful! So I have to do some research why the hive PE_.Default has not been unloaded before the dism /commit. Perhaps the original user is called INSTALL?
Thank you for the right direction.
PS: How do I add a "(Solved)" to the title?
Glad to hear the issue is solved, go back to the initial post of the topic and you should be able to edit the subject line to add the [Solved] indicator.