DISMTools

Sadly, the Info messages aren't useful. You'll need to look at the end of the file so that you can find "Error" messages

 

Regarding your suggestions:

1. The main purpose of this tool is not to debloat Windows images. Sure, you can debloat images in some ways, but DISMTools was never meant to do just that
2. Same as reason 1 - you may be able to add Edge in the future, but the program isn't a debloat tool. Besides, uninstalling Edge is pretty hard, considering that it is so integrated into Windows
3. You can remove AppX packages, which some may classify as "bloat" (mainly due to the ads Microsoft shoves down your throat in the Start menu of Win10 and Win11) but, like all other reasons, DISMTools is not a debloat tool
4. You could automate service management by using unattended answer files that call a PowerShell script that does service manipulation. The Store is an AppX package, so this goes with number 3

 

Windows Defender

Code:

Blocked by: Attack surface reduction
Rule: Block abuse of in-the-wild exploited vulnerable signed drivers

Have had this rule enabled (set to warn) for some time,
in theory the setting should allow me to choose what to do, but Defender simply overrides any decision.

The same thing literally happened a half an hour later when updating my VPN
to stop any further inconvenience, have now disabled this feature in Defender.

 

Well, if it starts working for you again, it may be better to leave it disabled. Besides, the best antivirus is common sense.

 

... definitely on the same page. By the way Great Tool.

 

Italian translations are complete. They'll take some time to appear in the latest nightly installer though, as testing needs to be done now.

​

 

Planning for the PE Helper's extensibility has started and my idea is to create a special project that contains standard project files, ISO content files, projects, and more. Here is a concept:

​

What do you think, and what should be changed?

 

You need to login to view this posts content.

 

The extensibility of the PE Helper is now complete. Soon, it will be merged with the current work for Preview 1

 

DISMTools 0.5.1 has seen improvements regarding the reporting of operation errors. If a custom description is unavailable for an error code, it will now use the one from the Windows APIs instead of a generic string telling you to look for the error codes online. This will still happen if it can't get the error description though.

​

 

An interesting tip is that you can specify custom DISM API libraries to add support for newer images on older operating systems. Drop "DismApi.dll" and the "Dism" folder from the newer OS (or from a newer ADK) into the root folder of the DISMTools installation and re-launch the program:

​

Note that if you're copying stuff from the ADK, you must manually create a "Dism" folder and copy every provider DLL to it.

 

Stub package options for AppX packages have been implemented:

​

This option is enabled if all these conditions are true:

• The DISM executable is from Windows 10 or a newer version
• The image you're servicing contains Windows 10 or a newer version
• The package you're dealing with is a bundle package containing stub packages (which are defined in the AppX bundle manifest with the "IsStub" property)

​

Otherwise, it is just disabled and the application will be added normally

 

You need to login to view this posts content.

 

Now, you can add Microsoft Update Manifest (MUM) files to target Windows images:

​

​

 

Soon, work on the July 2024 Update of DISMTools 0.5 will begin, and one of the features that will be backported will be the DIM. This is a quick heads-up of one of the features that will arrive in that version.

Also, it won't be released alongside Preview 2 of DT 0.5.1, which is expected to come out next week, because I want this release to be special. You'll understand more of that when this month ends

 

thank you for work sir posibe language default lp's my langue fr_fr winPE or boot wim svp

 

You need to login to view this posts content.

 

Work on Update 1 of DT 0.5 has started, and new features have already arrived:

​

 

The initial implementation of the Windows Image Explorer is almost complete, now with back/forward navigation and navigation with the address bar. Please report any issues you may have with it.

 

Now, nightly installers will be generated every day at 9 PM GMT+2 (7 PM UTC) using a cron schedule. This allows performing quick corrections to buggy code without waiting for installers to be generated. Now, if you want to get the latest builds without waiting, you'll need to follow the build instructions.

That's what should have happened. I learned that schedules trigger a run on the default branch the hard way. The WIM Explorer will keep its scheduled action unless it's also broken.

I consider this a really weird day. First with the CrowdStrike issues that have been affecting everyone in the world, and now with CI/CD issues. For DISMTools, the old method has been reinstated.