MSMG ToolKit

No problem. Good luck.

I doubt there's any regular registry cleaner that will do what you want. It'd be best to use PShell.

IIRC, you have to remove the packages after doing a few things in the registry in order for their registry entries to also be removed:
- Navigate to HKEY\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages
- Change visibility to 1 (Set-ItemProperty -Path "HKLM:\$RegistryKey" -Name Visibility -Value 1)
- Add a DWORD value "DefVis" and set its numerical value to 2 (New-ItemProperty -Path "HKLM:\$RegistryKey" -Name DefVis -PropertyType DWord -Value 2)
- Remove all the subkey owners (Remove-Item -Path "HKLM:\$RegistryKey\Owners")
- Use PShell or DISM to Remove-Package

I will try this on one of my server VMs after I finish the script for it.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Hi!

Found a simple way to fix Windows sidebar Shortcut Entries creation in desktop.ini file.

<%InstallMount%\ProgramData\Microsoft\Windows\Start Menu\Programs\desktop.ini> (before Sidebar ShortCut Entries Creation)
Encoding : UCS-2 LE BOM

Code:

[.ShellClassInfo]
LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21782

[LocalizedFileNames]
MiracastView.lnk=@%SystemRoot%\MiracastView\MiracastView.exe,-1002
Immersive Control Panel.lnk=@%SystemRoot%\ImmersiveControlPanel\systemsettings.exe,-650
PrintDialog.lnk=@%SystemRoot%\PrintDialog\PrintDialog.exe,-1002

<%InstallMount%\ProgramData\Microsoft\Windows\Start Menu\Programs\desktop.ini> (after Sidebar ShortCut Entries Creation)

Code:

[.ShellClassInfo]
LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21782

[LocalizedFileNames]
MiracastView.lnk=@%SystemRoot%\MiracastView\MiracastView.exe,-1002
Immersive Control Panel.lnk=@%SystemRoot%\ImmersiveControlPanel\systemsettings.exe,-650
PrintDialog.lnk=@%SystemRoot%\PrintDialog\PrintDialog.exe,-1002
楓敤慢⹲湬㵫╀牐杯慲䙭汩獥尥楗摮睯⁳楓敤慢屲楳敤慢⹲硥ⱥㄭ〰വ ; <---- Sidebar ShortCut Entries

FIX:

Code:

    :: Checking If Desktop.ini File Already Contains Windows Sidebar Shortcut Entries.
    findstr /i /c:"Sidebar.lnk=" desktop.ini >nul

    if errorlevel 1 (
        :: Creating <Desktop2.ini> File to Fix Encoding Error For Others Locales Than English.
        for /f "tokens=* delims=" %%z IN ('"type desktop.ini" 2^>nul') do echo.%%z>>desktop2.ini
        echo.Sidebar.lnk=@%%ProgramFiles%%\Windows Sidebar\sidebar.exe,-1005>>desktop2.ini
        del /f /q desktop.ini >nul
        ren desktop2.ini desktop.ini >nul
        attrib +h +s desktop.ini >nul
        cd "%ROOT%" >nul
    )

My Test Config:

Host OS : Windows 7 SP1 fr-FR (Updated) x86
Guest OS : Windows 8.1 ir5 (x64/86) | Windows 10 (10240/14393) x86/x64

 

To Kenafri good job dude

 

Hey guys ,

I tried the toolkit 7.1. with the creators update and found some bugs. Additonally I've added the .250 Update before removing components.

Please have look at the screenshots. What are you think about it ?

 

You need to login to view this posts content.

 

Nope, I downloaded a fresh iso already with the Mediacreation Tool and one by one started to remove windows features, and tested them in VirtualBox, once I removed:

[A] Microsoft Biometrics
Microsoft Connect App
[C] Microsoft Maps

The problem started to appear again, I did nothing inside the mounted folders etc.

I could try to re-install the toolkit and see if that helps.

 

Thanx Tiger-1 !

But, all congratulations go to MSMG for his hard work on Toolkit .

 

...

 

triple post...

 

For some reason the downloaded Dutch MCT image is not converting to a wim file it's not detecting te Install.esd.

[3] Convert MCT Image to WIM Image

Cannot Find Windows Setup "Install.wim" Image in <DVD\Sources> folder...

Please Copy Windows Setup "Install.wim" Image to <DVD\Sources> folder...

Btw the MCT image is an ESD, so does the tool look for the .wim or is this just a typo?

 

I'm sorry, MSMG. I was to fast by posting.
Thanks for your reply. Good to know the percent numbers are alright.

Yes, it's winsat (winsat formal -restart clean).

 

I'd also put it at the root of a drive since there's very little chance of anything blocking its access to the actual packages it removes.

Unfortunately, as stated, I've only ever had the problem you're having when I've sysprepped and ended up making a stupid mistake in my unattend.xml. Weird.

 

It was already on the root drive, i'm testing it now with an english iso. Thanks for the suggestions anyway!

Edit1: Same problem on the english iso with a fresh toolkit installation.

Edit2: I decided not to remove to mutch just the preinstalled apps and onedrive/telementry services all is fine now

 

yep Kenafri of course MSMG is the creator of most useful tool for Windows O.S.