unfortunately, I use the updated dedup by murphy78, this conflict error only happen if u integrated that into offline image, even I've removed the package, the wim is broken, so it's not the matter it need to be updated or not, it affect other package too (maybe it detect as windows server that's why it have conflict with RSAT?)
Well I don't actually use De-Dup for my personal systems and so haven't tested it on real time how it affects with other components of os. I will either test it myself or will ask help for murphy and moderate about this issue. right now I have finished extracting mui packages for windows 7 games. still vista and xp games mui files are left and so the next version of toolkit is getting late.
Code: ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ MSMG ToolKit - Select Source ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ ------------------------------------------------------------------------------- ░░░░Selecting Source WIM Images░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ------------------------------------------------------------------------------- Listing Available WIM Images for Servicing... =============================================================================== | WIM Index | WIM Arch | WIM Image Index Name =============================================================================== The system cannot find the file specified. =============================================================================== Enter the WIM Image Index's # [Range : 1-] : seem that MSMG Toolkit in my system dont detect the install.esd file in the DVD/sources folder... is there something i need to install first? or im missing something?
i thought it is supported according to the Changelog v1.07 + Added Support for Decrypting Encrypted Windows Store Updated .ESD Image Format, while Selecting Source.
The ToolKit supports Windows 8.1 Store updated ESD Image and it does automatically converts the ESD Image to WIM Image using Apply & Capture VHD Method. You can find the screenshots in the first post to know how it works. The new version of ToolKit which is yet to be released uses the different method for converting Windows 8.1 Store updated ESD Image to WIM Images which takes less time than the Apply & Capture VHD Method. Do check your source files for read only attributes and clear them and then try again. At present The Toolkit don't support Regular WIM -> ESD Converted Images.
ive read the instructions but the toolkit just dont detect the install.esd and donbt offer the convertion of install.esd to install.wim.
Is your Host OS Windows 7 or Windows 8.1 ? Do you use the ToolKit inside the Documents/Download/Desktop Folders if so then Do you use any space in your user account name. If there is a space then the toolkit won't work properly. Also do check whether the source install.esd file is not corrupted if it's corrupted then the ToolKit will display such errors.
ive tested it in windows 7 and windows 8.1 both in x64. i placed the toolkit in "C:\W81". how do you test the install.esd for corruption? and im customizing a windows 8.1 AIO removing a couple of images so it will decrease the iso size so it will be less than 4gb to test if windows 8.1 in usb drive will boot an iso.
Of fine, when you select the first option from the ToolKit i.e Select Source Menu, did it asked for ESD to WIM Conversion ? I can see from the screenshot you had provided earlier, its asking for Index No. But you say your source is a ESD Image and this is the thing which is getting confused. You are also saying that you are customizing a Windows 8.1 AIO, is this AIO your source OS which contains the install.esd. then it's a regular WIM->ESD Converted Image and not Windows 8.1 Store Updated ESD Image. To know whether an ESD Image is not corrupted, you can use the DISM commands to check the Integrity of the ESD Image or you can install the OS and see whether the ESD Image gets installed properly. If you can briefly explain what's your source image like where you got it from, probably i can find out what's the error.
i think it's a regular WIM->ESD Converted Image and not Windows 8.1 Store Updated ESD Image. i downloaded a customized windows 8.1 AIO image. it didnt ask for the ESD to WIN Conversion.
Ok, so its a regular WIM-ESD Converted Image.. The ToolKit at present doesn't support the regular WIM->ESD but in future I will add support for it.
After using this tool for integrate the update 1 and others kbs,when install windows(live installation) i cant make work WU(windows update)says...error,analysing whith tool MS accuse corrupted WU....Why? (I used windows 8.1 Embedded for this)
Interestingly i faced that error likewise after integrating latest May Updates. Although i did it manually the error is the same so i guess it's not related to MSMGs tool . Would be interested in a solution too.
Yes,Slave77,if i do integration update 1 only,i can use WU very well,but if i integrate others kbs including kbs this month,WU dont work..