Free MustangPE & Free Plugins For True Image Home 2011-2013 & Disk Director 11 Home
Hi Rick,
Run MustangPE and click the "Check Paths" button. Is the path to the WAIK OK? If it is, try running MustangPE "As Administrator."
Hi Paul,
I checked that path button numerous times, when clicked it says WAIK path okay, I even installed autoit-v3-setup.exe so it's path would prompt okay too, which I toggle that in on the Advanced tab.
I just ran it as Administrator and same thing, it says it created the iso in the C:\MustandPEBuilder\ISO\winpe_x86.iso, but it does not show up there or anywhere on the HD.
I'm using the latest i7 setups with SSD's if that makes a difference but I don't think so.
An interesting tidbit is I've now also installed your MustangPEBuilder 2 ADK version with TI 2013, and that version yes does create a winpe-86.iso just fine, I've made a DVD with it too, and I booted it and it works just fine, and I've even made a backup.tib of C:\ while I was at it so that I can re-image it back in at any time, which happens fast here.
Next morning edit:
Testing it all again the next morning.....
I love the fact that your ADK version has that create a USB option.... sure I could of done it myself, but it's rad that you did in your program!
I see importantly you have a Time Zone set which is helpful for correct time stamp on image creations too.
Testing them I see that USB naturally boots MustangPE v2 soooo much faster than the DVD, it's a no brainer here.
I really like the Quick Launch bar with stuff, and the Start button with same....
...Really really really really nice job Paul !
Okay, Any more suggestions with the Mustang PEBuilder v2.238 saying it's created the iso, but the iso not showing up?
Thank You
PS,
I'm going to test and switch out my partition images to TI v11 and go get the v11 plugin from you and see if that works, since it's really that v11 plugin I want for all the, important to me, GUI and location reasons I prefer v11.0.0.8101 (or better yet v11.0.0.8326....wink) to create and explore my images, but I do use either 2011 or 2013 to restore them for old school unique partition Alignment reasons, but that's another subject.
I have all the versions from day 1, registered, of TI & DD in my collection, but I do have my favorites for sure.
Glad to hear the ADK version worked for you. I can only guess as to why the WAIK version is not working. What version of the WAIK have you installed? My website points to a download link for WAIK version 3.0 of 1.7 GB dated 8/6/2009 under the Details tab. This version has been tested in MustangPE. I also see a WAIK supplement of 1.3 GB dated 2/21/2011. This WAIK has not been tested with MustangPE.
Yes I downloaded my AIK from your link and installed the same v3.0 one for sure, nothing else; I've even reinstalled it today but no difference.
I've now tried many many times, all paths are good, and prompts say succeeded, but the iso itself does not physically appear using the AIK MustangPEBuilder on either a TI v2013 Home install, or a TI v11 Home install.
ADK produces the .iso for both versions just fine though.
I've done everything I can with AIK and don't mind trying things you suggest if you want to clarify the issue just in case it's relevant to more than just my setup.
In the meantime more importantly I have a more pressing matter with the new v11 plugin I just got.
Using ADK, everything checks good and all prompts succeed as it builds the bootable USB fine, and it boots fine, and TIv11 comes up fine, however when I get to the point to create an image and clicked to start, as soon as it starts, it ''instantly'' stops and throws up an error, see attached picture, but nothing is listed as a cause and no physical log is created anywhere, and of course no .tib is made either.
Using the installed Windows TI 11 and just creating a USB bootable out of it's own windows options, that bootable works fine today creating images, as it always has, but I made a new one today anyway, and of course today have made images via Windows on it too. yes chkdsk done, plenty of room on that backup partition, etc, etc,
Somethings up with the ADK using the vTI11 plugin with the way it operates and accesses/boots True Image v11 'within that environment' on my setup I guess. Now this is what I want to resolve please, v11 is the whole reason of my visit here this week.
Thank you, and awaiting your feedback.
I'll attach a screenshot of that GUI error, not that it's going to help you though.
edit with a tibbit.
interesting is that the error picture of how the TI GUI appears in ADK is just like it appears using it in windows Except in Windows that System State warning (even though cosmetic only) is Green and its needs satisfied, but the plugin accesses it in its fresh install state and displays Yellow with what it says. The True Image 11 program made USB GUI does not even have a System State visible at all - none of which matters I'm sure, but it must just be the way plugin usage vrs windows accesses the program.
Hi Rick,
Very interesting. I just did a full test with TI 11 build 8101. The ISO was successfully created. It booted fine. TI 11 ran OK. When I tried to do a full disk backup of the C drive, I got the same error you got. I don't know why. I know it worked in 2009 with whatever WAIK we had available at that time. I don't have time to troubleshoot this right now.
I got around it with a quick and dirty workaround. I ran MustangPE Advanced options and checked the box to pause the build. I ran the create ISO again and when the build paused, I copied TrueImage.exe (13,777 KB) from C:\Program Files\Acronis\BartPE\BartPE\Files to C:\winpe_x86\mount\Program Files\Acronis\TrueImageHome replacing TrueImage.exe (15,981 KB). Now the backup ran without any errors.
Hi Paul,
Yes that worked okay, and the image it made restores okay as well.
I can see on the About Box naturally swapping those exe's changes the build number from 11.8101 down to 11.8054 though.
Only a little has changed according to the release notes between the builds, however it is a little unnerving that the engineers never updated the plugin in sync with build 8101 causing this to happen, who knows what unforeseen conflicts there may be though. We can't be the only ones that noticed this can we? I know not many use v11 anymore and I only do for specific reasons of my own, but it's hard to believe that no one else has ever noticed this over the years isn't it?
Thank you for coming up with a workaround in the meantime, appreciated.
Hi Rick,
I've found the problem with the TI11 plugin not being able to perform a backup in MustangPE. A needed file called shfolder.dll is missing from X:\Windows\System32. Apparently, shfolder.dll was included in the WAIK I was using when the plugin was written. The WAIK we are now using does not include shfolder.dll. Just run MustangPE again with a pause and copy the 32 bit version of shfolder.dll from C:\Windows\System32 to C:\winpe_x86\mount\Windows\Sytem32. This should solve the problem.
Hi Paul
I did exactly as you outline, but it comes up with the same error.
I ran the test twice, to be 100% sure.
I used the ADK test created directly to USB to boot, that TI v11 Home is installed on my Windows 7 partition right and that's where I have been testing it, and so at that I used the shfolder.dll out of 7 as well.
I'm sure you do since you cannot 'standard' install v11 on Windows 8 anyway and so that must be where you're testing this too right? unless you have gone virtual, but I am not.
Hey Paul,
Okay I just tested the new corrected plugin you sent me, thanks, and it all works fine now.
Nice work!
True Image shows the correct version number too now of course, 8101
~~~~~~~~~~~~~~~~~~~~~~~~~~~
I would like to solve that AIK MustangPEBuilder 2.238 issue from my post #151 as well, it has to be something simple why the iso is not showing up even though it says it is, and so if you can think of what I could try with that then please mention it. I have that all setup still and have not put that partition image to bed, yet.
Perhaps you were using the previous WIAK which I believe was, vista_6000.16386.061101-2205-LRMAIK_EN.img
Anyway that's not as important, but it's just an itch to get scratched is all. I like the ADK to USB, but again still would like to see the AIK through when time permits.
I have Windows 8, and Vista too, and so unlimited in where I can test this.
Hi Rick,
I looked back at post #151. You say you got the message the ISO was created at C:\MustandPEBuilder\ISO\winpe_x86.iso. I noticed Mustang is spelled wrong. Did you install it there or was that just a typo when you posted?
Hi Paul,
Yes it was just a typo on my part.
I have edited, and properly re-written the whole #151 post, with screenshot.
https://forum.acronis.com/forum/17630?page=3#comment-194234
Please advise
Thank you
Hey Paul,
For a hunch, I just un-installed WIAK for Windows 7, and then installed the slightly older version of WIAK which its file was called:
"vista_6000.16386.061101-2205-LRMAIK_EN.img"
I extracted it, and installed it.
Guess what - the winpe_x86.iso shows up fine now Running WIAK with Mustang PEBuilder 2.238
Glad you got it working.
Well yes but no, because I see now that yes it made the iso fine and is when I posted and left for dinner, but back and now to test the iso, and so separately burning that to USB and then booting it, is the no, because it actually will not fully boot properly and is non-functional.
I was hoping looking forward to see your WIAK version of Mustang PEBuilder 2.238 in action, but not tonight I guess.
As you said it seems to be something with WIAK but the version I installed sure at least made an iso appear, but a useless one.
I'll leave the rest up to you since it's your program and surly you know well what you are doing. I was hoping to be of assistance and help. I've just imaged back to Win7 WIAK in minutes to before I uninstalled it, and so can test any ideas going forward if you have them.
One more question. Is your Windows 7 system you are using to build MustangPE a 64 bit system?
Windows 7 Pro SP1
32 bit
I've tried it a few times again checking everything I could think of this morning, even made sure the shfolder.dll was in the C:\winpe_x86\mount\Windows\Sytem32 and it was. It seems everything works fine, the iso just does not appear.
We are using the same system. I tried again with a fresh install of the WAIK and a fresh download of MustangPE_2_238 and it works. I can't do anything else to help you. Just be happy the ADK version is working for you.
Okay thanks for checking it, I appreciate your time.
Yes ADK is nice.
One of the reasons it's important for me to understand why the .iso won't actually show up in your WIAK version, is simply because I need to make sure my fully developed install of Windows 7 Pro doesn't have anything amiss with it that may affect another operation I'm not aware of, even if it's a little thing. It would be helpful to know what it is for my own piece of mind if nothing else.
Just to test some more I booted to my Vista SP2 partition, and installed WAIK for Windows 7, ran MustangPEBuilder_2 there, and Yes here on my Vista partition it created the .iso just fine, then I separately created a USB boot disk and then booted it ...and that worked fine too; I even created a backup tib with TI, and fwiw, I'm happy to see the AIK version also has Copy/Paste ability from txt files to and from within the TI Comments Box.
To test more I booted to my Windows 8 partition, was glad to see that WAIK for Windows 7 installed just fine there too, ran MustangPEBuilder_2 and Yes on my Windows 8 partition it created the .iso just fine too...
So there has to be a simple reason why WIAK MustangPEBuilder_2 won't produce an .iso on my Windows 7 install when it says it did. I'm up to try any suggestions. Does anyone have an idea? I've read the whole thread now, and I see there's a lot of accomplished techs here, and wondering if any of you have run into this or have some guidance?
Thank you
Rick,
As a next step, I would suggest doing a clean install of Windows 7 and testing again. If it works, you will know something is wrong with your existing Windows 7.
Fresh install, well, my pristine Windows 7 install has been a year in the making, meticulously installing all my special softwares and updates as I went along, and of course at the same time creating backup .tib images along the way.
I have dozen backup .tib images of that Windows 7 history saved.
For the fun of it, just to scratch that itch to know what the cause is, on a second test computer setup I started restoring .tibs backward to see when this 'not-appearing iso from MustangPBuilder' would work and when it would not, and wouldn't you know it, darn it, all the way back to the 2nd image made nearly a year ago, where it works fine! As you can imagine much was done installing and setting up softwares since then, but looking at the list, None Of Which, should have affected that operation.
I'll try a few things to see if I can isolate it, I've already started checking and trying things - no doubt I know I Can Find the nit, but, is it worth my time since with this earlier image I Can Now Make A Working WIAK MustangPBuilder winpe_x86.iso and use it on my current setup... but my tenacity to know and fix my master Windows 7 install of what the issue is beckons at me, however it has always run flawlessly since I installed it. I'm in a Quandary since to install fresh would be very time consuming for such a minor? issue. (The difference between WIAK and WADK installs shows up in backup .tibs @ an extra 5 GB!)
While I decide what to do going forward, in the meantime every once in a while I'll peck at my test setup and see if I can isolate it without messing with my main setup which I need always active. In the interim suggestions welcome, but surly it may be anyones guess at this point since anything from a-z could of foiled it.
Once a MustangPE disk is made, it may be used on any computer.
Try running sfc.exe /scannow on you Windows 7 to see if it finds any problems.
Okay will try SFC shortly
Here's an interesting observation with the not appearing .iso
During testing on my current install of Windows7 with your AIKMustangPEBuilder.exe and making a WinPE.iso, is while testing it, I had the C:\MustangPEBuilder_2\ISO folder in focus (opened) (it was empty) ...and I had the AIKMustangPEBuilder.exe open in focus too and I clicked the Create WinPE.iso button and it went though its things, and "right when the prompt came up" saying that "ISO Created at: C:\MustandPEBuilder\ISO\winpe_x86.iso" ...right when the prompt came up, my eyes caught for a split second, the winpe_x86.iso appeared and then as quick as it was there - it disappeared. I thought I was seeing things, so I did the procedure again and this time was ready with fingers and highlighted and ctrl/v on it, before it disappeared, but then it was gone and as I pressed ctrl/c anyway this is what as you would expect came up (attached screenshot)
This may give a clue Paul as to what's going on?
ps, now just a glancing thought
I noticed at one other time in the ADK version if you told it to write the .iso to USB but if you forgot to put the USB stick in, then your program would automatically put it in the .iso folder, but it would not do both. Now in this your AIK version, is there some code you have that it would move the .iso in certain conditions? (trust me though it's no where else on this Hard Drive, but my point it, what in the world would remove it 1 second after it appears? ..is a good question right! (no not my AV or anything like that, tried all disabled etc no effect) Yes I realize I am probably the only one that has this issue, understood, and for me on a new install it's fine, but just consider it for a moment as to the cause... thanks
Any thoughts?
Once a MustangPE disk is made, it may be used on any computer.
Yes okay thank you, but for True Image to work, it needs to have a version of True Image installed and have that specific TI plugin for it, yes. I mean it can't run the TI plugin if there is not True Imaged installed. Some of my OS's may or may not have a certain TI version installed or not, some have different version for different reasons. That's why a standard TI boot disk is nice, it runs on anything, and can create images even if TI is not installed or irregardless of which version is install on said computer, right?
ps
(SFC running now)
Edit:
No Running SFC did not solve the problem
Try running some of the commands that MustangPE uses manually to determine if you get any error messages.
Go to Start Menu/All Programs/Microsoft Windows AIK and right click Deployment Tools Command Prompt and select Run as Administrator. Then enter the following commands and note any error messages. Be sure to type the lines exactly because any typos will cause error messages.
copype x86 c:\winpe_x86
copy c:\winpe_x86\winpe.wim c:\winpe_x86\ISO\sources\boot.wim
imagex /mountrw c:\winpe_x86\ISO\sources\boot.wim 1 c:\winpe_x86\mount
imagex /unmount c:\winpe_x86\mount
oscdimg -n -bc:\winpe_x86\etfsboot.com c:\winpe_x86\ISO c:\MustangPEBuilder_2\ISO\winpe_x86.iso
You should get the iso file at c:\MustangPEBuilder_2\ISO\ as long as that folder exists. If you don't, what are the error messages?
When you are done, delete the c:\winpe_x86 folder.
Edited to correct images mount command.
Thank you Paul for the reply
Okay, there was one error I circled in Red on the Attached Screenshot, however! the winpe_x86.iso 'IS' in my
C:\MustangPEBuilder_2\ISO folder ...yeay!
My mistake on the mount command. There needs to be a / in front of the word mountrw.
imagex /mountrw c:\winpe_x86\ISO\sources\boot.wim 1 c:\winpe_x86\mount
Download http://www.mechrest.com/plugins/MustangPEBuilder\Downloads\Files\MustangPEBuilder.zip . Unzip the file to get a debug version of MustangPEBuilder.exe. Temporarily use it to build a MustangPE iso. Follow the directions when it pauses during the build. Let me know when it goes wrong.
Okay thank you much, and this time it worked clean as shown in the attached screenshot
The winpe_x86.iso shows up in it's folder.
Now why does it work fine for me this way, but not with running the AIKMustangPEBuilder.exe and the iso disappears?
Edit:
I see you posted minutes before me and so I haven't done you last post yet, this post is in regards to the one before with the /mountrw
Download http://www.mechrest.com/plugins/MustangPEBuilder\Downloads\Files\MustangPEBuilder.zip . Unzip the file to get a debug version of MustangPEBuilder.exe. Temporarily use it to build a MustangPE iso. Follow the directions when it pauses during the build. Let me know when it goes wrong.
All previous prompts were valid, but it goes wrong here at Prompt 3 (attached) ..the winpe_x86.iso appears in the \ISO folder for 1 sec and disappears
Try again. When the build pauses at Build paused after image in unmounted, but before iso creation, open the Deployment Tool Command Prompt as administrator and manually enter the oscdimg command to create the iso. Check to see if the iso is created before continuing. What happens?
When the build pauses at Build paused after image in unmounted, but before iso creation, open the Deployment Tool Command Prompt as administrator and manually enter the oscdimg command to create the iso. Check to see if the iso is created before continuing. What happens?
Doing as you said above, the .iso gets created and 'is' in the \ISO folder and stays there!
Then if I go back to your application and click continue on the Pause Prompt, it deletes the .iso !
...and finishing out the prompts it never comes back.
Well just copy the iso out to another folder before continuing.
Yes okay I did that of course.
I was hoping this would tell you something as to what's up? ..and why?
You don't have to do anything special with it on my behalf for sure, I'm good, you've done enough thank you for sure, but if by chance this disappearing iso act affects anyone else going forward, you have this information in mind now to be of help.
Thank you for your work, it's much appreciated!
It has to be some kind of Windows permission issue. I've seen this type of thing before where you can do an operation from a command prompt, but Windows won't allow a program to perform the same operation.
Yes it's something that must of happened along the way as shown in my testings ever since that 2nd backup image of this Windows 7 build many months ago.
I'll figure it out when time permits if necessary, not that I need to since I have what I need to go, but just because for the fun of and hunt of it.
I have everything set very permissive as I do a lot of software testings, but I've never seen this issue until now though, so it surprised me.
Again I just thought 'if' it was something in your program I offer to test things to fix it if it would help others if there's more than just me, but if it's just me no problem, I have both your ADK & IAK USB boot disks for each version of TIv11 & v2013 so I'm good to go, and if I need to make one again then with your oscdimg workaround at the pause thanks to you (which btw works for both that debug & regular version) it's easy and more than fine for me.
Thanks again for checking it.
I don't want to belabor the other question, but I sure wish there was a way on a Regular TrueImage boot disk to add a little ditty that would allow a copy/paste from .txt or pre-made script or whatever, allowing to insert pre-typed text into the True Image Comments box during a booted session.
PEBuilder is awesome for so many things, but (afaik) when using it with True Image it needs a version specific TI install on the OS with its BartPE plugin, but there are times when I need to Image when no version of TI are installed, or a different version of TI is installed on the OS that's other than what I have a premade PEBuilder of, and in those cases a regular TI boot disk is pretty much unlimited in creating/restoring images, and that's where I would like the ctrl-c & ctr-v or similar to work. Is that possible?
The regular boot disk is based on the Linux operating system. You would need to do a lot of homework to figure that out!
As I said before, the WinPE versions of TI (including MustanPE) may be used on any computer just the same as the Linux version. It does not matter if TI is installed on that computer or not.
My sincere apologies, I feel like an sleep deprived nummy to have asked that question again....
I misinterpreted what it said on your website when it said:
1. You must have the Acronis product installed on the computer you are using to build the CD for the Acronis plugins to work.
Obviously I know it has to be installed to create it in the first place, but somehow in my lack of sleep testing I interpreted that also to mean it needed to be installed afterward too and so never tried it, duh!
I just used your ADK version with TI Plugin included burned to a USB boot stick, booted it and did anything/everything I wanted to do with or without TI installed on the OS.
I'll play with the AIK later, need some sleep now....
Thank You so much for your time and patience, appreciate it greatly.
One more thing to try before we put this to bed. Download http://www.mechrest.com/plugins/MustangPEBuilder/Downloads/Files/Create… . Unzip the file to get CreateISO.exe.
Make sure C:\MustangPEBuilder_2\ISO is empty. Run the debug version of MustangPE up until you get to the pause before iso is created point. While MustangPE is paused, double click CreateISO.exe and see what message is displayed. Do you get an iso at this point before resuming MustangPE?
Hi Paul,
You are one smart techie to pick up on this before I even mentioned it and having me get a new download, because before when I said that the AIK iso that was created with the oscdimg command workaround was fine, I had so many windows open on two computers I think I neglected to focus on this error within the oscdimg command box (attached) when I created that iso and one comes up, and then later when I secondary burned it to USB and booted it - would not boot correctly. I was so mentally burnt though I needed a break so I didn't mention it to you out of fear of TMI... and only posted that the ADK worked perfectly which it did!..love it, but truth is that the oscdimg USB or CD burn of the iso would not boot correctly. I had tried it 3 times, same error. Don't 100% the thought just yet, was mentally burnt so human error could be a factor. It was on a build that had Windows AIK & ADK installed at the same time if that matters, whereas yesterday I was on a build that only had WIAK.
edit:
I see you posted a create.iso and I'll test it now to see what that gives.
Very interesting. Run the debug version again and leave Windows Explorer open. After you click the Create WinPE ISO button, navigate to C:\winpe_x86\ISO\sources in Windows Explorer as fast as you can. You should see only one file called boot.wim. Up until the pause before image is mounted, there should be no TMP file seen. When you continue, some TMP files should be seen. When you reach the pause after image is unmounted, all TMP files should be gone. When the iso is being created, you should not see any TMP files.
Let me know what you see. If TMP files are remaining after the image is unmounted, then that is the point that is going wrong.
The Create.iso gives: winpe... Does Not exist.
The Sources folders has the boot.wim, but also has 119 .tmp files in it as well, but that is when it's on the 3rd Pause.. unmounted, but before iso creation.
I'll do it again because you are also asking what's there before it's mounted.
FWIW, on the 4th Pause after iso file creation, still has boot.wim, but also has 119 .tmp files
5th Pause, after wimpe has been deleted - is true, it's gone, but right along no actual iso file gets created in the other ISO folder except for that split second when it hits the 3rd Pause is where that happens, the winpex86.iso appears for 1 second and then disappears.
edit:
Let me do the first and second pause, give me a minute
The first Pause, only the boot.wim is in the Sources folder
The second Pause, only the boot.wim again
heading toward the 3rd Pause, the .tmp files multiply and hmmm, this time instead of 119 it has 121 various .tmp files, then the rest is as written above
Paul, you do realize as I mentioned yesterday, I can image my OS partition back (in 3 minutes flat) to the second build of this particular run of my current Windows 7 install which was 8 months ago, where at that point this disappearing iso act does not happen (no windows updates etc were done yet either, it's pretty much a fresh install) ..and I can run MustangPEBuilder_2 and it does produce an iso and it does not disappear and I can use that to create a boot USB ...which I should have done yesterday when I tested it, but lost track of the iso and have already replaced that image as testing went along. My point is, I don't mind testing this current disappearing iso scenario to see what's up if that's what you want to do; I'm just as curious as you are, but if it's positively just my current install glitch and could ever be anyone else's, then.... well just keep that in mind. If it could happen to others, then it's more worthy of understanding.
edit:
fwiw, I see I had created a backup image of yesterdays test on that 8 month ago build (I'm not surprised I did that either) ..and so I have that available for testing and/or to easily restore the the image or individually grab that winpe_x86.iso that it made)
edit:
fwiw I did just that in 5 seconds, I restored just the individual winpe_x86.iso that was in its ISO folder
I burned it to USB and booted it and it works fine, but I can't believe that it only has A43 and PENetCfg on it, so somehow and for whatever reason I didn't have the TI plugin installed. Well no problem I can easily just restore the entire image and incorporate the plugin edit: exploring that image I see why now, I had the Seagate version of True Image installed at that particular build stage, and so would have to install the Acronis version on it, but the point in testing that was for the minimum which was seeing at which point in time that my Windows 7 backup .tib history was working with your AIK version.
Anyway, I will test anything and anyway that you want to Paul
Rick,
You can stop anytime you want.
My next step would be to take ownership of the C:\winpe_x86\ISO\sources folder and assign full control to Users. You can try this at the first pause. The fact that the TMP files are not being deleted is the problem here. I see no more than 4 TMP files at one time, but the names are changing as they are being deleted and new ones are being created. When the image is unmounted, all the TMP files should be gone.
When you reach the first pause, right click on the C:\winpe_x86\ISO\sources folder and click properties. Click the Advanced button. Click the Owner tab. Edit ownership and select the User account. Close the properties window and reopen it. Edit the permissions and assign Full Control to the Users account. Close the properties window and continue the build. Keep watching the C:\winpe_x86\ISO\sources folder to see if the TMP files now get deleted. Does this help?
sorry took me longer because I wanted to do it a few times and give full control to everything and every listing since it did not work the first time with still 121 .tmps, but every time there was 121 .tmp files, changing somewhat like you said, but always full.
I'll show a screenshot but it's a long one so one would have to open it with the options set in Internet Options Advanced to not resize images in browser IE which is the Only way I always have that set anyway.
I can still test any good ideas you have, but that's up to you.
There is a problem, and a cause, and a simple answer to fix it, but knowing what that is eludes at the moment
I guess that's all we can do. It's Microsofts' tool (dism.exe) that is failing to delete the TMP files during the unmounting of the image. Now that taking ownership of the folder didn't help, I don't know what else to try.
Okay, I've gotta run because so much around the house and things to do, but you can bet I'll come back to play in the days or weeks to come, and if I have an important development to tell I will post. Likewise pm or post if you have any ideas that pop up via enlightenment moments.
I will also restore that beginning image that works that has no disappearing acts, and test that the same way too...I'm curious how many temps it will have. You can bet I will install True Image on that build and create your AIK version of MustangPEBuilder and burn it to USB to have both ADK & AIK versions.
Okay, thank you, and all the best...