Hello MSMG. Can you upload polish language pack for Windows 10 16299.15 X86/X64, including: FOD, LP and Win PE? If it will not be a problem to you, can you tell me how to extract all necessary files from polish DVD to copy all files myself? Thanks in advance
Trying to figure out why Dishonored 2 won't running. The Nvidia 385.69 and the Wu Driver 387.87 in pairing with a gtx 1080 won't help. When I start the game it give me a black screen and all I can do is to click the reset button. With a win 10 1703 msmg toolkit iso there where no problems with gaming. Does anyone has the same problem?
Updating my windows is it ok ? Its wont update any components that i have removed ? or mess somehow else my windows ?!
The best route with System Apps is not to delete the packages from the image; rather, to prevent their provisioning and installation entirely during the Windows Installation process. When Windows installs, it checks the InboxApplication parent-key in the registry and provisions all apps that are present as child-keys. By removing the child-key corresponding to the System App, Windows is prevented from provisioning that System App and installing it into the system. Moreover, with this route, the directories and manifests for the System Apps remain on the system so the system sees all the corresponding System App files and directories and will never fail updating, all health servicing commands work as they should, etc. Lastly, remove the Run key for SecurityHealth, and disable the Services from running. All of this can be done on an offline image by loading the HKLM\Software registry hive. If you do not want to fiddle with ControlSet services in an offline image, you can take a registry file and use an OOBE.cmd to merge it with the registry during setup: Code: Windows Registry Editor Version 5.00 ;Windows Defender Security Center Service [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SecurityHealthService] "Start"=dword:00000004 ;Windows Defender Antivirus Service [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDefend] "Start"=dword:00000004 ;Windows Defender Antivirus Network Inspection Service [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WdNisSvc] "Start"=dword:00000004 ;Windows Defender Antivirus Network Inspection System Driver [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WdNisDrv] "Start"=dword:00000004 ;Windows Defender Advanced Threat Protection Service [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sense] "Start"=dword:00000004 "Start"=dword:00000004 = Disabled "Start"=dword:00000003 = Enabled Name the reg file with the above entries "defenderdisable.reg" and create an OOBE.cmd then simply add... Code: regedit /s "%WINDIR%\Setup\Scripts\defenderdisable.reg" ...to the OOBE.cmd Add it to the install.wim, or use a Configuration Set ($OEM$ folder) to transfer it over during installation. I do not want to hijack this thread, but I can provide a piece of my personal script that does all of this in a For/Do loop, and you can also disable any other System App you wish. Simply send me a message. When it comes to System Apps, I cannot stress enough how removing the packages entirely from the image is not the proper way to go about creating a custom image. **EDIT** I did nothing else with this image other than ran a quick For/Do loop to disable Defender/Security Center from provisioning (and added a clean Start Menu layout); I applied no further offline registry hive optimizations nor did I remove any actual App Provisioned Apps. But because I removed the SecHealthUI child-key from the offline install.wim registry hive, Windows never installed it during the actual installation of the OS since the key was not preset to tell Windows to do so. Security Center and Defender are completely MIA and none of their packages were removed. As you can see, all the files for it are still on the system (this ensures Windows Online Servicing never snags, nor do updates ever fail).
I am not going to say what is good and not good for people to do with their own system builds because everyone's different; however, the Creator's Update specifically is very picky when it comes to complete System Application removal, especially since Cumulative updates will now check to see if the integrity of various Apps' directories are in-tact and online servicing (e.g. sfc /scannow) will either return incorrect results or fail to repair corruption, even if you supply a source ISO/WIM. Not to mention, System Apps are not isolated packages like Appx Provisioned Packages. System Apps are linked to dozens or more system services, Group Policy templates, registry entries, WMI objects, etc. and because of that, one's safest bet is to simply prevent their installation instead of deleting the packages entirely. The registry key removal does nothing other than make that specific System App invisible during Setup when Windows provisions and installs them. The System Apps' directories, manifests, ADMX templates, etc. all remain on the system. Though the WIM itself doesn't get lighter, since packages are not being removed, the system's integrity remains optimal as well as its longevity without issues. This is the way we go about "removing" System Apps using MDT/SCCM/any type of server deployment because it does not interfere with GPOs, will not throw security warnings galore or give alerts about filesystem corruption. And yes, that $OEM$ folder goes in the sources directory on your USB stick, CD, whatever and it will automatically disable all of the Security Health Services/Defender services before OOBE completes. Just make sure the registry is serviced offline before installing Windows. Shouldn't take more than 5 minutes, even if you do everything manually.
I'm a little hesitant on trying to walk you through making registry changes to offline image hives, simply because if you remove something you shouldn't, or change something you shouldn't, your image will be broken before you even install it and I don't want that happening. I'm certainly not insinuating you're incompetent, but miscommunications do happen, amd when it comes to something like modifying an offline registry, it's usually easier to give someone a script to do it than try to instruct them where to go, the commands to enter, etc. It's not hard...basically you mount the install.wim and then reg load the specific hives that require modifying. 99% of things can be done simply by mounting the HKLM\Software hive since other hives such as HKEY_Classes_Root filter to Software\Classes as well as HKCU (Current User). If you were to mount your install.wim to C:\mount, you'd access the hives by loading them from the offline image, into the online registry for editing. So if I wanted to have my Software hive loaded under something recognizable, I'd select something like "WIM_HKLM_SOFTWARE" so I can clearly see it's the loaded WIM Software hive, and I'd do that by typing: reg load HKLM\WIM_HKLM_SOFTWARE "C:\Mount\windows\system32\config\software" as the Software hive is located in the System32\config directory (most are). Then, after modifying what I needed, I'd unload the hive by typing: reg unload HKLM\WIM_HKLM_SOFTWARE There are a ton of How-To's all over the web. Again, I just do not want a miscommunication issue and have you do something that ends up ruining your image.
This may have been asked before, but is it possible to get good old Paint (for integration) back in RS3, just like Calc32? In cab format preferably, not through Store... Or is there a better ultra-light and ultra fast and ultra simple image editing non-store app out there?
Are there any Inbox Apps, like Defender, that must be enabled/set in registry for OS to install and function (obviously the disabled Inbox Apps would not function). BTW, where did you get all info on how RS3 will check fore files than RS2 and even package removal through DISM (method MSMG Toolkit uses) would result in unfixable SFC errors? You are pretty much saying that using MSMG Toolkit on RS3 image is likely to prevent OS from updating... That has never been the case before...
My Understanding We can increase OS stability/integrity by leaving System Apps like Defender 'in place' and disabling them during installation. I can see the advantage of GodHand's generously shared method for someone who is rolling out a corporate-wide upgrade of 100's or 1000's of machines. My Question Will a PC behave the same or perform the same if you disable System Apps during installation verses disabling them using scripts or basic sliders after you've installed the OS? For example with Defender ... is the final PC performance (CPU cycles, memory requirements) the same if I turn off Defender using the OS GUI verses disabling Defender during installation? [Edit] I only have a few machines to 'service' … The question rephrased using the common tongue If we have to leave this bloated crap intact, why not just turn it off after installation rather than risk messing things up and wasting a bunch of time troubleshooting a botched install?
Hi, I remove many metro apps but I'd like to use the app Photos and I don't remove it (Option [Q]). with version 7.7 the app simply does not work, it's there any solution for this matter or I'm doing something wrong? At the second try I leave windows store (Option [V]), the app does not work either! Thanks! --edit Seems that the problem is with the ISO (clientcombined), all seems good with original ESD.
like this? but after the installation of the system, the Windows Defender Security Center Service continues to work.