MSMG ToolKit

Could the exporting option be used for this, it exports the indexes the user wants to keep and replaces the original wim with the new one?

 

@MSMG -Another suggesion:

Don't exit to the Main menu automatically from the [6] Apply until "Re-Build Source Images" is finished.
Often there are 3 procedures here and user may want to stay until the last step:

- Cleanup Source Images
- Apply & Save Changes to Source Images
- Re-Build Source Images

Also it will be fine for the newcomers, they will understand intuitively that they need to compress the image at the 3-rd step.
No need to go to the [6] Apply once again, this is really confusing (they have no idea the hidden sub-menu has changed for the next step).
And things will be faster for everybody.

 

Exactly the same as my script does . first export single index from main wim then move the exported wim to sources directory & rewrite it.
Win10 Tweaking Scripts Both Online & Offline

 

Try the MSMG 10.7 Beta. He made available for pre-test the functionality of selecting only the desired indexes in the DVD source.
I believe that will solve that detail.

Edit:
I just tested it.

The toolkit exports the Index you are editing, but does not delete the unwanted ones.

@MSMG, after saving the script could perform the deletion of the unselected indexes in the initial assembly.

Hypothesis: if you have 5 indexes and select to mount 2,4. Soon 1,3,5 are left over and could be excluded.

Edit 2:
I was reading what I wrote and I realized that I expressed myself poorly.

Hypothetically speaking: if you select index 2,4 from 5 options, then index 1,3,5 remains. So if the code reads in advance that these are the disposable indexes.
When @MSMG finishes implementing the selection of INDEXES in the same way that it is already working for the source assembly, a command could be added to call the WIMExport session right after finishing saving the image.
Or just take advantage that the necessary indexes are already identified and export directly to the current Install.wim. It makes more sense.

Maybe I'm thinking in a way that this part of the code might be repeating routines redundantly. It may be that this can be done directly at some previous stage, but I don't see much beyond that.

Raising hypotheses helps to improve or create solutions.

 

readTime: 47s

Hello everyone,

New to using this software as well as windows, but smart enough to evaluate the "readME" file. Wanted to refresh the device from scratch. It ran windows10 perfectly a week ago.

Process so far wiped the device (surfacePro2 w/512GB) via the microsoftSurfaceDataEraser. Downloaded a fresh copy of the surfaceRecoveryUSB from microsoft technical support site. Followed their odd install instructions of exporting a .zip folder to a prebuilt USB via recoveryDrive. Hard drive still shows as raw or 0-out in diskPart. I think it's missing the surfacePro2 drivers which I also grabbed from their technical support site. But believe I need to install vis MSMGToolKit.

diskpart/detaildisk/
disk ID:00000000
Type: SATA
Status: Online
Path:0
Target:0
LUN ID:0
Location Path: PCIROOT(0)#PCI(1F02)#ATA(C00T00L00)
Current Read-Only State: No
Read-Only: No
BootDisk: No
Pagefile Disk: No
Hibernation File Disk: No
Crashdump Disk: No
Clustered Disk: No
There are no volumes

Using ToolKit_v8.8
After converting the install.SWM files to .WIM and trying to mount the DVD get the following error.

##Source Image Information##
The syntax of the command is incorrect.
"c:\Users\####\Desktop\project\w81\wim\Bin\x64>"

QQ: What am I missing?

 

Hi,

Put project folder into C:\ and try again.

C:\project\

 

Thanks for the rapid response. Tried that, still no dice...
The host is a win10 machine but the install.wim is a 8.1 pro.

Using ToolKit_v8.8
Tried editing the toolkit.cmd wadkToolsPathVariables to point at the win81DISM.exe

if %HOST_Version% equ "6.1" set "DISM=%~dp0Bin\%HOST_Arch%\DISM81\DISM.exe
if %HOST_Version% neq "6.1" set "DISM=%~dp0Bin\%HOST_Arch%\DISM81\DISM.exe​

MSMG Toolkit - StartUp - Confirms this as true
DISM.exe = c:\project\Bin\x64\DISM81\Dism.exe

DISM Log
Dism.exe version: 6.3.9600.17029

Haven't tried implementing any packs. Don't know where to begin there. At 12.93gb its quite large.

Thoughts anyone?

 

Quick question here: Does modifying a Windows installer introduce problems when trying to install Cumulative updates?

 

Yes only if image servicing is done without knowledge . means if user remove defender or firewall then WU always will result in a error on minor CU updates ie Preview Updates & same apply on EDGE too

 

I have not had any issues for quite some time install CUs on modified images BUT in the past there were cases where you would frequently see issues.

It is hard to predict what changes MS will make in the future that could cause problems.

 

hmm maybe i'm wrong, but because people complicate things so much unnecessarily; I just think we should follow the master and everything will be solved from the first Toolkit, at least here, there were few times that I had problems

 

Hello great master, I have a question: by the way our master will not update more modifications in the older operating systems will I be correct? because if so I will discard everything we have worked on since the beginning of W8.1 by the way M&FT won once and for all or stay with Windows 10 or any open source system or I am wrong thank you master

 

"Acquire new knowledge whilst thinking over the old, and you may become a master for others".

--- Confucius ---

 

@MSMG

could you look into adding this in
https://forums.mydigitallife.net/threads/quick-hack-20h2-enablement-without-edge.82154/

This is what I do with my custom script, export only the ones user ask for.
move to temp do all the work on that and then delete old and move exported one back into the initial location rename it back to original.

 

I know,I know,

“温故而知新，可以为师矣”,Acquire new knowledge whilst thinking over the old, and you may become a master for others