Yup. I downloaded image 22621.1 from uupdump. Using MSMG Toolkit v.13.6, SSU 22621.2567 and KB5032190 (22621.2715) were successfully integrated into the image. After that, I removed everything except ClientCBS, CloudExperienceHost, ShellExperienceHost, StartMenuExperienceHost, UndockedDevKit, FirstLogonAnimation, WindowsMediaPlayer, Windows Photo Viewer, NotepadApp using the "Remove" menu in the toolkit. And I still get an error when installing Windows. So, such a guide really won't hurt.
Toolkit works great did another 22h2 22621.2283 iso yesterday and last night was installing it. everything works as it should. the only real issue theres with the toolkit is that after you install windows and use resetbase, dism scanhealth will throw errors but i found easy fix to fix dism by installing next any update then simply removing it no more dism errors.
I asked you if it was a comment block, as the batch code is between: <# comments here #> This makes the code unusable in PowerShell, as it turns it into a simple comment block. My previous code may contain quotation marks errors, but that's because I didn't know what you were doing, it was a suggestion that didn't work, but OK. I also think there may be something breaking your cmdlet, since the get-partition codes I sent didn't work in native Powershell. Have you tried using the code as it was before, but using cmd.exe? Code: cmd.exe /C "PowerShell.exe -nop Invoke-Expression ('$OldDrive = """"%1""""; $NewDrive = """"%2""""' + [System.IO.File]::ReadAllText('%~f0'))" or Code: cmd.exe /C 'PowerShell.exe -nop Invoke-Expression ("""$OldDrive = """"%1""""; $NewDrive = """"%2""""""" + [System.IO.File]::ReadAllText("%~f0"))' or Code: cmd.exe /C 'PowerShell.exe -nop Invoke-Expression ("""$OldDrive = """"%1""""; $NewDrive = """"%2""""""" + [System.IO.File]::ReadAllText("""%~f0"""))' The above code may also contain quotation marks errors. You can try if you want to. To avoid using batch script convert the code to powershell using args[] that I suggested. Take this test too. I got tired of coding in PowerShell and having to adjust everything for each system. In my codes I only maintain compatibility with native PowerShell 5.1.
hi there @inTerActionVRI does imck allow you to use a deploied image as the source? that is to say, I have applied a windows image using dism. can that applied image be used in your wonderful imck? thank you for reading my question sir, also thank you for all of the custom developments with imck. Majid
Hey, is it possible to remove the Classic Calculator from Windows 10 LTSC 2021 and how does it work with this tool or are there instructions for it?
Yes Calculator can be removed, This list shows what can be removed. Spoiler: RemovePkgsList_W10_LTSC_2021.txt Code: EdgeChromium InternetExplorer FirstLogonAnimation GameExplorer LockScreenBackground ScreenSavers SnippingTool SoundThemes SpeechRecognition Wallpapers WindowsMediaPlayer WindowsPhotoViewer WindowsThemes WindowsTIFFIFilter WinSAT OfflineFiles OpenSSH RemoteDesktopClient RemoteDifferentialCompression SimpleTCPIPServices TelnetClient TFTPClient WalletService WindowsMail AssignedAccess CEIP FaceRecognition KernelDebugging LocationService PicturePassword PinEnrollment UnifiedTelemetryClient WiFiNetworkManager WindowsErrorReporting WindowsInsiderHub HomeGroup MultiPointConnector RemoteAssistance RemoteDesktopServer RemoteRegistry WorkFoldersClient AccessibilityTools Calculator DeviceLockdown EaseOfAccessCursors EaseOfAccessThemes EasyTransfer FileHistory Magnifier ManualSetup Narrator Notepad OnScreenKeyboard Paint ProjFS SecurityCenter StepsRecorder StorageSpaces SystemRestore WindowsBackup WindowsFirewall WindowsSubsystemForLinux WindowsToGo WindowsUpdate Wordpad AADBrokerPlugin AccountsControl AddSuggestedFoldersToLibraryDialog AppResolverUX AssignedAccessLockApp AsyncTextService BioEnrollment CallingShellApp CapturePicker CBSPreview ContentDeliveryManager ClientCBS CloudExperienceHost CredDialogHost ECApp Edge EdgeDevToolsClient FileExplorer FilePicker LockApp MapControl NarratorQuickStart NcsiUwpApp OOBENetworkCaptivePortal OOBENetworkConnectionFlow ParentalControls PeopleExperienceHost PinningConfirmationDialog PrintDialog QuickAssist RetailDemoContent SearchApp SettingSync ShellExperienceHost SkypeORTC SmartScreen StartMenuExperienceHost UndockedDevKit WebcamExperience WebView2SDK Win32WebViewHost WindowsDefender WindowsMixedReality WindowsReaderPDF WindowsStoreCore XboxCore XboxGameCallableUI XGpuEjectDialog
It's totally my fault. Sorry. I asked a question about the powershell storage commands not working. Then I posted some code that works perfectly, on vanilla PCs. There is no issue with how the code is written. I regret posting the code. This caused the whole discussion to shift away from my original question into one of coding techniques. As someone else, posted. there are lots of ways to write code. Can we please stop talking about the code. There is nothing wrong with the code. The question is "What components must I retain the ensure powershell storage commands work". I asked because an untouched vanilla W10 works perfectly. It's only the images I've created with MSMG that don't work. The response was (if I understood it correctly), was to do a "process of elimination", which would take me weeks (Start with full image, remove one component, test, rinse, repeat). In the end, I've got new code that uses diskpart and not powershell and works perfectly even on my modified windows images. I guess this will just go down in history as unsolvable. Yes! Correct! But it's not my code that's breaking powershell storage commands. They are broken in native powershell on ALL PCs. And that's all I wanted to fix.
Hi, Binary testing means you select half of the options and see if things work or not. Based on the outcome, you keep repeating the halving on the path where the issue comes from. So, for instance, if at selecting first half of changes still have issues, you halve those changes and narrow it down from that group with keeping half of the changes of the group after each test. If you do not have issues after applying half of the changes, it should be coming from the other half, so you do this process for them. It is really fast, and very rarely should you have parts in both groups where only using them combined breaks something. I did this some months back when I had search issues in Start Menu (then someone reminded me that he already reported it some pages back actually). I would be happy to help you out with that, would need to have your source image and exact steps you are doing, which I am sure you mentioned already, but it's difficult to recover the proper information at this point. It does not take too long, even though the removal works rather slow with the Toolkit. Since I absolutely have no idea what you were doing (basically TL/DR), my guess is that (if you are using Component removal from the menus) it's originating from System Components, and the testing should be focusing on them. Backup, Storage related entities sound suspicious to me. Keep in mind that there are like 15 active members here, and from what I can tell, only you and I use PowerShell in a serious manner. Command line (cmd) should not be involved at all if you can call PowerShell, so that only adds more options for failures, even though the effort is appreciated. Also, posting bugs that you are already aware of does not help (quoting issues that I spotted immediately). My last image is from v13.3 and I did not notice any issues to be honest - thought I am not using these specific commands, everything seems to work just fine. We had one guy from India some months back, where he thought he removed something, but it turned out he had ISP problems and Web pulling commands he used from a downloaded script were getting Timeout. If you are using an "unsupported" image, the Toolkit will do unexpected things - since it is closed source, I must assume it works on certain patterns for each version, hence it needs to be updated, which is definitely not optimal, nevertheless the efforts are still appreciated. And no, pure version match is not enough, Edition needs to be correct as the Toolkit is seems to have data hardcoded for it. (I did promise an alternative method for applying updates several months back, but I was also having ResetBase issues, and wanted to sort out them by having a stable image before publishing anything, which has not happened to this date and I am about to get back on the project and testing around January 2024.) We are playing around with a Black Box with our own (non-standard?) input and we are barely in control of the output, it's a miracle we have such high success rates actually. Your problem is not as difficult to solve as you think, try what I suggested above (hopefully ELI5 enough, otherwise Google maybe) or let me or others help you, but we need your image and exact steps for sure.
Allow me to post a workaround that seems to give you what you need as far as I could understand reading back. It seems that my old image is also broken for such commands and thus I could find the component myself actually - the system where I apply updates already restored the broken components, so they work there. I did seem to find other, native commands that still work on the broken system and should give you what you are after, you should give a try to the following commands: Get-WmiObject -Class Win32_LogicalDisk Get-WmiObject -Class Win32_Volume Get-WmiObject -Class Win32_DiskPartition Let me know if these do not cover what you are after. Should these commands be good enough, I can find the component myself if you do not wish to spend time on it yourself. Update: hope it is nothing new, but the commands will give you more detailed output when you pipe Format-List * after them. Feel free to use aliases, I prefer using the fully-qualified command names.
@tempdrive1 All good. I've got the script using diskpart now. Works like a charm. Maybe one day, when I have some time, I'll try and track down why PS storage commands don't work. I need to move on Now, I'm trying to figure out why office clicktorun is filling my c:\windows\temp folder with 100's of telemetry log files.
If I use MSMG TOOLKIT for debloat Win11 22h2 iso and after debloating it, I applied the update to win11 23h2 with DISM, would the debloat remain?
So to debloat the 23h2 iso you just have to wait for an update? There is no possibility otherwise right?
I have not yet implemented the use of removal menus with DISM for Online use (I understood what you said, as installed Windows). I think it's better to make a dedicated tool for this.
@Ace2, As far as I know, when updates are applied, the components that return are those that were removed through menus 1 to 7. Menu 8 (Windows Apps) components are not affected by the CU application. Unless something has been changed in the latest updates.
I dont think all components will return likely very few like defender and such or not even and it depends on what update you will apply. For example myself installed debloated 22h2 621.2283 then to fix dism resetbase installed kb5032190 major update for 22h2 not even defender was reinstalled and it was removed earlier with toolkit all i could see new was backup app in start menu, could be that if i updated to 23h2 i would get some apps reinstalled. best way is to try it doesn't take much myself happy with 621.2283