Search the Community
Showing results for tags 'ADK'.
Found 1 result
Hello everyone, I was just wondering if anybody came across the problem I had today using wintoolkit and ADK 8.1 Preview. I have an x64 VAIO which runs Win7 SP1 x64 Ultimate, a pretty fresh install, nothing except for IE10, office 2013, 7 zip + a few required updates/hotfixes. Today I installed ADK 8.1 Preview which features the new DISM 6.3.9431.0. Installing netframework 4.5 (also a preview) was required to install ADK. I installed WinToolkit and tried to do some customizing on a win7 sp1 x64 ultimate (digital river disc). I mounted install.wim using cmd (by the way, very fast with amd64 dism) and then went on to WinToolkit's component remover. The component remover finds the already mounted image and after pressing "select" it tries to load it. And here's where the problem is: Normally the whole process of getting the list of packages takes 3-4 minutes but here it started with "checking if the wim is mounted" (the message on the bar). This lasted around 20 minutes, meantime it gave me an error ("The exception unknown software exception 0x40000015 occurred in the application at location 0xfe94aa8e"). Some other time the application just didn't respond and crashed and generally during this process of "checking if the wim is mounted" I was unable to even open an explorer window. Anyway, this time after "checking if the wim is mounted" it went on to "getting/unhidding packages", all that stuff. It lasted another 15 minutes and finally got me the list. The list, however, consisted only of few things: themes, remove winsxs, remove upgrade folder, that stuff, no other packages listed. I have no idea why the component remover does "checking if the wim is mounted", and why it all takes so long and then the list is missing all the packages. If I mount the image directly via WinToolkit something like this never happens. Also, when I mount the image with e.g. gImageX and then go to Wintoolkit to process the image, everything is fine. I used to do a lot of mounting directly in Wintoolkit as well as mounting the image with command line and the go to wintoolkit. Never have had such a problem before, though I used WAIK at that time. By the way, when I use the ADK 8.1 dism commandline, it works fine, it's fast. All the get-packages/features, mounting, anything I tried was OK. I don't know which version of dism is being used by Wintoolkit or wether it matters at all. Any idea what the problem may be? is it possible that the new dism is different or mounts the image in a different way? maybe it is the 4.5 framework? Cheers eveafterdark