Ok, so it says extraction failed and leaves system folders in temp. Now, can anyone say how could I delete the files in temp and go for another extraction this time using wim?
MSMG is indeed a great tool, but as with any script or code that does things in batches, it's best to be modest with what you do.
Yeah...but...before it used to work fine with esd conversion, now it says extraction failed. It's the first time I came across with this. I should've read the earlier posts before trying the 7.2 version. I think all those system folders can only be deleted either by changing owner permissions or formatting the drive. I should've manually done the esd conversion to wim
It's your responsibillity to be sure the used source is not corrupt, that's not what i talked about. I always use MSDN/Techbench iso's, they can be easily verified.
Updated the ToolKit to v7.3 Edit: Forgot to mention the credit for abbodi1406 for the Microsoft .NET Framework 4.7 Pack (Windows 7) in the changelog. Changelog v7.3 + Updated ToolKit's Bin Folder with Windows 10 Redstone 3 Insider Preview WADK (v10.0.16190.0) Tools. + Fixed a Bug in the Feature "Select Source from DVD", Where the Display of Source Image Information was not Correctly Displaying the Image Description. + Updated the Feature "Integrate Microsoft .NET Framework 4.7" to Support Windows 7 Source OS. + Added Microsoft .NET Framework 4.7 Pack (Windows 7) for MSMG ToolKit (Thanks to MDL Member : abbodi1406). + Updated Microsoft DirectX 9.0c Pack for MSMG ToolKit with Fix for Folder Permission and Office Protected View Issues (Thanks to MDL Member : AeonX). + Fixed a Bug in the Feature "Integrate Windows Sidebar", Where the Windows Sidebar Integration was not Working for Some Languages.
I will have to read farther back so I can get an idea as to what problem you're having. The only issue is I can't offer much in respect with MSMG since I did not write it and use my own PShell and C++ scripts to do everything since I use the DISM API.
Which ESD Image are you trying to convert, is it a Windows Store Downloaded ESD or Media Creation Tool created ESD or a custom one?
Its Education ISO created by MCT. And abbodi's esd to wim converter worked fine. I don't think the ISO I have downloaded is corrupted since I'm able to extract it via 7zip as said by you in the earlier post.
Right now I don't have an MCT Image to test out, But you can try with the new version of ToolKit and see if it works. Since the new MCT Images are ESD images with .esd extension, so I have made changes to the ToolKit to read .ESD as input instead of .WIM You can either use one of these menus and both should work, the second one will only convert the first index. - Convert ESD to WIM Image - Convert MCT to WIM Image Will merge this two menus to one for next version after a proper testing with a MCT Image.
Is the winsat error that I posted a few pages behind fixed? Maybe it's phrased out in an other way in the changelog?! I couldn't test wireshark on the weekend. We had to organize a birthday party . But again if someone had already checked it out with win10 untouched and an win10 toolkit edition a feedback would be nice.
Oh I forget something. I think there were problemes with updates in the past wenn you killed windows store completely. Do I have to keep anything of the store for updates?
I usually don't use the WinSAT but today checked with WinSAT formal -restart clean command and i think it's working Code: C:\Windows\system32>Winsat formal -restart clean Windows System Assessment Tool > Running the Formal Assessment > Running: Feature Enumeration '' > Run Time 00:00:00.00 > Running: WinSAT Direct3D Assessment '-aname DWM -time 10 -fbc 10 -disp off -normalw 1 -alphaw 2 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock' > Assessing Desktop Graphics Performance > Run Time 00:00:13.38 > Running: WinSAT Direct3D Assessment '-aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)' > Assessing DirectX Batch Performance > Run Time 00:00:00.39 > Running: WinSAT Direct3D Assessment '-aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)' > Assessing DirectX Alpha blend Performance > Run Time 00:00:00.36 > Running: WinSAT Direct3D Assessment '-aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3' > Assessing DirectX Texture load Performance > Run Time 00:00:00.36 > Running: WinSAT Direct3D Assessment '-aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3' > Assessing DirectX ALU Performance > Run Time 00:00:00.36 > Running: WinSAT Direct3D Assessment '-dx10 -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)' > Run Time 00:00:00.02 > Running: WinSAT Direct3D Assessment '-dx10 -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)' > Run Time 00:00:00.00 > Running: WinSAT Direct3D Assessment '-dx10 -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3' > Run Time 00:00:00.00 > Running: WinSAT Direct3D Assessment '-dx10 -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3' > Run Time 00:00:00.02 > Running: WinSAT Direct3D Assessment '-dx10 -aname GeomF4 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 150;200;241 -batchcnt C(50);C(200);C(300) -objs C(12);C(26);C(45) -noalpha -geomf4shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1' > Run Time 00:00:00.00 > Running: WinSAT Direct3D Assessment '-dx10 -aname GeomV8 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75;100;120 -batchcnt C(25);C(100);C(150) -objs C(8);C(17);C(29) -noalpha -geomv8shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1' > Run Time 00:00:00.02 > Running: WinSAT Direct3D Assessment '-dx10 -aname CBuffer -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75 -batchcnt C(25) -objs C(8) -rendertotex 6 -rtdelta 3 -texpobj C(1) -cbuffershader -cbufa 2 -cbuff 5 -cbufp 6' > Run Time 00:00:00.00 > Running: Media Foundation Playback Assessment '-input C:\Windows\Performance\WinSAT\winsat.wmv -nopmp' > Run Time 00:00:07.81 > Running: Extended Media Assessment '-input C:\Windows\Performance\WinSAT\Clip_1080_5sec_VC1_15mbps.wmv -video offscreen -audio mute -prevent3pc -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog' > Run Time 00:00:10.80 > Running: Extended Media Assessment '-input C:\Windows\Performance\WinSAT\Clip_1080_5sec_10mbps_h264.mp4 -video offscreen -audio mute -prevent3pc -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog' > Run Time 00:00:10.17 > Running: Extended Media Assessment '-input C:\Windows\Performance\WinSAT\Clip_480_5sec_6mbps_h264.mp4 -video offscreen -audio mute -prevent3pc -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype int2fps' > Run Time 00:00:09.38 > Running: Media Decode/Encode Assessment '-input C:\Windows\Performance\WinSAT\winsatencode.wmv -encode C:\Windows\Performance\WinSAT\winsat.prx' > Run Time 00:00:10.95 > MOOBE Run Time 00:01:05.47 > Running: CPU Assessment '-encryption -up' Warning: The RDTSC to QPC delta is too high ( CPU 0 ) > Run Time 00:00:03.13 > Running: CPU Assessment '-compression -up' Warning: The RDTSC to QPC delta is too high ( CPU 0 ) > Run Time 00:00:10.08 > Running: CPU Assessment '-encryption2 -up' Warning: The RDTSC to QPC delta is too high ( CPU 0 ) > Run Time 00:00:03.14 > Running: CPU Assessment '-compression2 -up' > Run Time 00:00:10.39 > Running: CPU Assessment '-encryption' Warning: The RDTSC to QPC delta is too high ( CPU 1 ) Warning: The RDTSC to QPC delta is too high ( CPU 0 ) > Run Time 00:00:03.23 > Running: CPU Assessment '-compression' Warning: The RDTSC to QPC delta is too high ( CPU 1 ) Warning: The RDTSC to QPC delta is too high ( CPU 0 ) > Run Time 00:00:10.30 > Running: CPU Assessment '-encryption2' Warning: The RDTSC to QPC delta is too high ( CPU 0 ) Warning: The RDTSC to QPC delta is too high ( CPU 1 ) > Run Time 00:00:03.27 > Running: CPU Assessment '-compression2' Warning: The RDTSC to QPC delta is too high ( CPU 0 ) Warning: The RDTSC to QPC delta is too high ( CPU 1 ) > Run Time 00:00:10.23 > Running: System memory performance assessment '' Warning: The RDTSC to QPC delta is too high ( CPU 1 ) Warning: The RDTSC to QPC delta is too high ( CPU 0 ) > Run Time 00:00:05.09 > Running: Storage Assessment '-seq -read -n 0' > Run Time 00:00:11.19 > Running: Storage Assessment '-ran -read -n 0' > Run Time 00:00:14.56 > Run Time 00:00:00.00 > CPU LZW Compression 83.95 MB/s > CPU AES256 Encryption 62.97 MB/s > CPU Vista Compression 235.98 MB/s > CPU SHA1 Hash 221.64 MB/s > Uniproc CPU LZW Compression 41.34 MB/s > Uniproc CPU AES256 Encryption 31.50 MB/s > Uniproc CPU Vista Compression 118.23 MB/s > Uniproc CPU SHA1 Hash 110.17 MB/s > Memory Performance 4555.18 MB/s > Direct3D Batch Performance 42.00 F/s > Direct3D Alpha Blend Performance 42.00 F/s > Direct3D ALU Performance 42.00 F/s > Direct3D Texture Load Performance 42.00 F/s > Direct3D Batch Performance 42.00 F/s > Direct3D Alpha Blend Performance 42.00 F/s > Direct3D ALU Performance 42.00 F/s > Direct3D Texture Load Performance 42.00 F/s > Direct3D Geometry Performance 42.00 F/s > Direct3D Geometry Performance 42.00 F/s > Direct3D Constant Buffer Performance 42.00 F/s > Video Memory Throughput 2005.87 MB/s > Dshow Video Encode Time 8.10000 s > Media Foundation Decode Time 1.89284 s > Disk Sequential 64.0 Read 55.90 MB/s 5.5 > Disk Random 16.0 Read 1.12 MB/s 3.2 > Total Run Time 00:02:30.73 C:\Windows\system32>
What problems did u faced earlier regarding store, I didn't had any issues with updating the OS when the store is removed.
I had no problems when removing the store but I think I read something here that it wouldn't be good if I want to use windows update but kill the store client. So I didn't touch the client. Sadly I don't find the posting with this info right now.
@MSMG, A unimportant (?) minor bug (?): If the ToolKit-vx.x.cmd file is in a folder with spaces between words, it can't detect other word of the folder. For example: I extracted MSMG Toolkit to this folder: "H:\Windows7-10\Windows Tools\MSMG ToolKit" And Selected to "1" (the "Source: Select Source from <DVD> Folder" ). ToolKit can't detect letters after than "H:\Windows7-10\Windows _". Of course, no problem in "H:\Windows7-10\WindowsTools\MSMGToolKit". I know, Quotation marks are required for folders containing spaces. And added as pre+suffix quotation marks to the %~dp0 variable. No fixed. Code: set "BootWim="%~dp0DVD\sources\boot.wim"" set "InstallWim="%~dp0DVD\sources\install.wim""
@MSMG I might make an updated video now. But since you mentioned that one needs to apply the Windows updates again after integrating the .NET Framework 3.5, is this the correct order? do I really need to integrate the Windows updates first before starting to remove stuff or can I just apply the Windows Updates as a last step and expect that all the stuff I removed are still removed? 1) Integrate all the features you want to add except for DirectX 9.0c and .NET Framework 3.5 using the Integrate Feature Menu. 2) Integrate the Language pack you want if required 3) Integrate the Updates. 4) Remove the Apps you don't want 5) Remove the Components you don't want 6) Apply Changes, this will perform the Cleanup 7) Re-Mount the Source 8) Add the .NET Framework 3.5 using the Integrate Feature Menu. 9) Add the DirectX 9.0c using the Integrate Feature Menu. 10) Apply Changes 11) Re-Mount the Source 12) Integrate the Windows updates again since we added the .NET Framework 13) Apply Changes 14) Create the ISO
Could you just leave the updates until last and only integrate them once? Or do you have to do it before and after .NET ?
Adding updates AFTER removing components adds some files like those related to OneDrive for example. But if you add the updates BEFORE removing the components you can update a system live via Windows Update and the files related to OneDrive are not added again. Tested by myself.
That's my question, thanks for putting it in a simpler way than I did. Awaiting @MSMG to reply before I make the next video