DISMTools does support servicing Windows 11 version 24H2 images, so this is a bit weird. Can you send in some screenshots?
Here are links to screenshots and logs(I don't know how to paste them here). Edit: I gave up on this.
Important news for developers using JetBrains IDEs: all projects are supported by Rider so you can open, build, and contribute to them. I've also performed a test refactor and a cleanup in the modified UnpEax project (C# project) and Visual Studio didn't seem to complain. If you encounter any issues, feel free to report them.
This change is now implemented in the latest nightly installer of DT 0.5. It will also make its way on an update to 0.4.2
In the hypothetical case that you were to add another installation image to your PE media, the PE helper now asks you what image to apply: You won't see this by default though - only if you have added multiple installation images to the "sources" folder. Also, since it is in that folder, "boot.wim" is excluded. After you've selected the image, you may not be able to go back to change it. This is because there hasn't been implemented a review screen so, unfortunately, you need to reboot if you chose the wrong image file.
I'm working on an experiment, which is in a separate project, that I think you'll like: Some features include custom properties and are currently shown as plain text. However, this experiment replaces that with a tree view: What do you think should be the way to show custom properties though? Let me know your feedback
You may encounter HTTP code 403 (Forbidden) when trying to get the feed news from the DISMTools subreddit: The weird thing is that getting feed news still works on Visual Studio and other places: All versions that support getting RSS feed news (0.4 - 0.5), including the updates to v0.4.2, are affected. I think it may be available for everyone in a few days but, if this is intentional from Reddit, I will explore other ways to provide not just feed news, but a dedicated website. If you run into this issue now and it is fixed in a few days, please let me know.
Fortunately, it was just a fluke on my end because it displays correctly for some reason now. Still, if you experience issues with this feature, please let me know.
I have a deployed windows located at V:\ The program qoutes this path when executing Dism. It gives an error. For example this command (similar to what the program tries to run) returns an error: Code: C:\Users\******>Dism /image="V:\" /remove-provisionedappxpackage /packagename=Microsoft.BingNews_4.2.27001.0_neutral_~_8wekyb3d8bbwe Deployment Image Servicing and Management tool Version: 10.0.22621.2792 Error: 1639 The command-line is missing a required servicing command. For more information, refer to the help by running DISM.exe /Image=<path_to_offline_image> /? where <path_to_the_offline_image> is the full path to an offline Windows image. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Yet this one succeeds (when the path is not quoted): Code: C:\Users\******>Dism /image=V:\ /remove-provisionedappxpackage /packagename=Microsoft.BingNews_4.2.27001.0_neutral_~_8wekyb3d8bbwe Deployment Image Servicing and Management tool Version: 10.0.22621.2792 Image Version: 10.0.22631.3447 The operation completed successfully. Is there some workaround for this? Thanks in advance.
Thanks for reporting this issue. It's all because I assumed that the program should add quotes every time an image was passed to the DISM command line. Now, I fixed a similar issue regarding captures of entire drives. Back then, I thought that would be it, but this was an oversight. I've implemented a possible fix for this which should come out as a nightly installer shortly. Performing deployment operations on standard mount paths still works after this change, but I haven't tested this with offline installations.