MSMG ToolKit

So I may assume that you guys use mainly portables?
An Office install with updates takes quite a bit of time.
With only Windows 10 on the drive a lot is still to be setup and in my case takes more than an hour, depending on system speed of course.

Cheers.

 

i have solved my problem with news iso in forum version 17134.1 i try first iso 2version of x64 home and pro
no cortana,etc sytem work

i search how to add drivers and microsoft package visualc++
it's necessary to change .cmd for add driver?


for futur version add:
mpc hc and vlc choice for video
musicbee or footbar for music
xnview for picture
notepad++ for write
open office

i use winxaero for add control panel menu in start menu(right click in logo)

Cortana in version 1803 is hard to disable

 

Cortana in any version isn't hard to disable... Just use a reg tweak and you're done.

 

I would like to integrate a bunch of stuff into my image. I know this question has been asked before, such as MSMG ToolKit, but I couldn't find specific answers.

Been googling for hours, and my eyes are tired and sore... Forgive me if I've missed the answers

I want to integrate

1. A number of registry entries,
2. My hosts file
3. Group policy settings (like Windows update to point to my WSUS server), login script, various others
4. Graphics Drivers

I have a bunch of PCs on 1703 and 1709 (16299.125 which need updating with the latest cumulative), and I want to build a new 1709 image with the above.

Could someone please point me in the right direction.

Thank you for your patience and understanding.

 

Is it possible to run multiple instances of MSMG Toolkit at the same time, as long as they are in different folders?

 

^ask directly to MSMG bro he can help you

 

Guys, is MS Game pack same as the one installed in W7 Ultimate? And does it work with W10?

 

Does anyone know what causes Windows Update 0x800736b3 to occur?

I removed all Windows components, advanced components (including Defender etc) and Metro Apps.

Now when I try to install the latest CU from Windows Update, I get this error! I'm happy to redo the image but could do with knowing what components/apps are responsible for this error code.

 

Same issue here (same components removed): Installation Failure: Windows failed to install the following update with error 0x800736B3: Update for Windows (KB4100403).

From CBS.log

Code:

2018-05-24 07:31:36, Error                 CBS    Exec: Failed to pend CSI transaction because transactions cannot be merged: 0. [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]

Tried to run sfc /scannow in an attempt to fix, but the result is not good: Windows Resource Protection found corrupt files but was unable to fix some of them.
(I don't know if this is related though.)
Scratch that. Below errors are caused by the WUMT Wrapper script.

From CBS.log

Code:

2018-05-24 18:14:54, Info                  CSI    00005626 [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UsoClient, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2018-05-24 18:14:54, Info                  CSI    00005627 [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2018-05-24 18:14:54, Info                  CSI    00005628 [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2018-05-24 18:14:54, Info                  CSI    00005629 [SR] Cannot repair member file [l:18]'WaaSAssessment.dll' of Microsoft-Windows-WaaSAssessment, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2018-05-24 18:14:54, Info                  CSI    0000562a [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2018-05-24 18:14:54, Info                  CSI    0000562c [SR] Cannot repair member file [l:18]'WaaSAssessment.dll' of Microsoft-Windows-WaaSAssessment, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2018-05-24 18:14:54, Info                  CSI    0000562d [SR] This component was referenced by [l:147]'Microsoft-Windows-Client-Features-Package001021~31bf3856ad364e35~amd64~~10.0.17134.1.microsoft-windows-client-features-deployment0010210-Deployment'
2018-05-24 18:14:54, Info                  CSI    00005630 [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2018-05-24 18:14:54, Info                  CSI    00005631 [SR] This component was referenced by [l:145]'Microsoft-Windows-Client-Features-Package00118~31bf3856ad364e35~amd64~~10.0.17134.1.microsoft-windows-client-features-deployment001180-Deployment'
2018-05-24 18:14:54, Info                  CSI    00005634 [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UsoClient, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2018-05-24 18:14:54, Info                  CSI    00005635 [SR] This component was referenced by [l:143]'Microsoft-Windows-Client-Features-Package0012~31bf3856ad364e35~amd64~~10.0.17134.1.microsoft-windows-client-features-deployment00120-Deployment'
2018-05-24 18:14:54, Info                  CSI    00005638 [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2018-05-24 18:14:54, Info                  CSI    00005639 [SR] This component was referenced by [l:147]'Microsoft-Windows-Client-Features-Package001021~31bf3856ad364e35~amd64~~10.0.17134.1.microsoft-windows-client-features-deployment0010210-Deployment'
2018-05-24 18:14:54, Info                  CSI    0000563a [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked

 

You need to login to view this posts content.

 

All is OK for me.

 

how to integrate language pack,?? and what i must download for this? i'm use win 10 1709 en-gb OEM but i want change to en-us,.. how to resolve missing language pack,i was download language pack and put to Packs\LangPacks\w10\x64\en-US ...,,,,

 

oh, that is mega link, i see

 

Put .cab file without rename to \Packs\LangPacks\w10\x64

 

I run LTSB and have no complaints here. Everything is running great got this system tweaked to perfection and am very satisfied with the results. With that said this was like a learning experience for me and will most likely sometime in the future use Toolkit 8.6 to trim down a more up to date release of Windows for sure.

 

I think I know what's causing the problem (for me at least).

I re-did the image but before saving/applying I tried to apply the latest CU and I got the 0x800736B3 error code. I checked the log and found this entry:

Code:

2018-05-25 10:03:27, Info                  CSI    00000736 TLC operation Uninstall incomplete for [7bfbf5e207aa69ed5ee85e89052ae572, version 10.0.17134.48, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]), missing compositions
    Microsoft-Windows-Application-Experience-Mitigations-C8, version 10.0.17134.48, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2018-05-25 10:03:27, Error                 CSI    00000737 (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #3845469# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150004]

I assumed "Application-Experience" was related to Microsoft Telemetry, so I re-ran the image up to the removal of the Telemetry, Defender, People Experience and SmartScreen, tried to apply the CU and it was successful.

So I tried building the image again afresh but this time I removed Telemetry and tried to apply the CU immediately afterwards. It failed with that error code.

I tried building the image afresh again, kept Telemetry but removed the other 3 components, tried to apply the update and it worked!

So for me at least, the removal of Telemetry breaks the installation of additional CUs.

 

Crap... I was already afraid the removal of Telemetry was the cause of the issues with KB4100403. Guess I'll have to start all over again. Well, that's the risk using MSMG Toolkit. Thanks for testing and confirming it, though!

I'm a little surprised we are the only ones that reported this so far. I assumed lots of MSMG Toolkit users would remove the Telemetry components. Perhaps we could fix it by re-integrating Application Experience afterwards... if that is at all possible. @MSMG ?

 

Of course, it's just a command window.

 

Question is more like if DISM allows multiple instances to be run. I remember seeing that you will get a logpath error.

Cheers.

 

DISM allows multiple instances. I do it all the time. You just can not run DISM more than once at the same time on the same file.