why sometimes msmg hangs until you press a button, like stuck at 65% until you come back and press any key, then it goes to 100%
After removing OneDrive, there is still component store corruption. Latest MSMG toolkit, LTSB spanish. Cheers.
Please be specific in which section it gets hanged. Also If you had clicked once inside the cmd window it will pause the operation and only continues until a enter key is pressed.
MDL user abbodi1406 hasn't yet updated the Add-on at WinToolKit forum, and also his previous add-on link wasn't accessible due to host been banned in my country.
The Component store and SFC corruption fix has been only applied to RS3 Windows Defender, SmartScreen, PeopleExperienceHost and few other components using the ToolKitHelper.exe method. Using the DISM method many times leaves behind some files/folders/registry keys which causes the error and other customization done like patching dlls for enabling extra features or skinning also leads to Component store and SFC corruption.
Hi Guys Im newbie in these things. Also my english is bad. Well, my question with the Toolkit is this. I created a custom ISO a Windows 10 Enterprise but I need Windows Updates not to run me automatically. Would to make it with Toolkit ¿?
I built 1709 images using MSMG and took out all bloatware, and several other components, added .NET 3.5, Directx 9.0c and classic Win32 Calculator and Paint. Each of the computers is using ClassicShell for the start menu. When the PC goes to sleep and is subsequently woken the taskbar, system tray and start button are unresponsive. Often this will mean a forced reboot. There is another problem too in that ALT-TAB in full screen programs will not display the taskbar. Now, I'm not suggesting this is MSMG Toolkit's fault at all. What I'm wondering is that one of the solutions suggested to "Fix the taskbar not working in Windows 10" suggests re-registering the taskbar. (Their words not mine). The suggested solution is this: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”} And then to delete the TileDataServer folder. I'm not a powershell expert by a long shot and would appreciate any thoughts on how this might end up given the de-bloated image I used to build the PCs. I'm asking here because the PCs were built using the images created by MSMG and I'm concerned that running this powershell command my "break" something because of the way the images were created. Sorry for my poor communication skills.
Please arrange the microsoft edge integration on windows 10 ltsb 2016. It even integrates with the try to open it simply opens and closes quickly. This error has been present since version 7.8 and to date has not been fixed.
Has anyone run into an issue where removing defender will leave smartscreen in an always on state? It means I have to go in and manually unblock every word file I want to open. Edit: I figured out a fix. You have to enable "Do not preserve zone information in file attachments".
What are you talking about? It works just fine, on both x86 and x64 LTSB. I've been making those images for months and there is no problem with Edge integration. Cheers.
I've just deployed the first LTSB image (x86) made with the toolkit 8.1. It runs fine, apart from the component store error reported earlier. That error seems not to matter that much so I just consider this a done job. Now on to x64. Cheers.
MSMG, I think the file ToolKitHelper.exe in your toolkit 8.1 is infected with the Win32/Azden.A!cl trojan. Windows Defender warned me about it and removed it. I replaced it with the file in toolkit version 8.0 and this one was fine. If you look a the size of ToolKitHelper.exe in the zip file of versions 7.8, 7.9, and 8.0, you'll see that this size is around 500 kb. But in the zip file of toolkit version 8,1, the ToolKitHelper.exe file size is almost 3 Mb. I think you should check this out.