@David Retzloff, can you show your configuration for the unattended file (it's on the previous page)? I'll give you the command line so that we can determine what's wrong
@David Retzloff, a nightly installer with the fix is on its way. Let me know if it works for you It was a parser problem
When you run into an exception, you will now see a new layout that lets you see more of the error. DISMTools will also do more reporting by showing its information (for example, program version and build time), which is useful to determine if the version someone is using is outdated or not. It also makes the closure policy clearer
The first beta of DISMTools 0.6 is now released. This release includes lots of changes and bug fixes. The portable version was released after the installer because of a release creation issue (due to attempts at automating creation) which caused the updater to not apply the update. It was reverted to manual creation
Base installed platform Windows 11 Pro (26120.1542) While testing the latest version 0.6 nightly preview with the latest Windows 11 beta (26120.1542) I was unable to save changes to the .wim. DISMTools was started as an admin. No permission restrictions on any of the source files I was was using (and had used previously). Just a general removal or install of apps, features, etc. Very vanilla. The first thing I tried was to remove the read only attribute for my working folder. Same results. Second was to take ownership of my working folder. This worked. I was able make various changes to the .wim and commit them after each step and while saving the final image. Odd issue and not a huge deal. I just hadn't run accross it with previous versions. I attached the last two DISM log sessions if you're interested. Going forward I'll just make sure I have ownership the of the working folders I use for DISMTools. Keep up the great work. Your project helps me more than you'll ever know.
Thanks for your feedback! Can you show me a video of what you're trying to do? It can help even more than just logs
Well, the log file in which I keep track of the DISMTools changes (see part 3 of the Fortnight) has now reached 60000 characters. This log file is incredibly long, having more than 1000 lines of changes. This has been a reliable source for looking at changes to be written in new releases ever since its creation, on January 2023, when I was ending the development of DT 0.2
I'll keep a video (or at least screens shots) of what I'm doing in mind for the next round of modifications. I've finished up what I was doing for this version of Windows 11. I'm waiting for the next Beta from MS. Thanks for the prompt response.
@David Retzloff, I can't seem to reproduce the issue on the same beta build of Windows 11 (26120.1542). You will have to send more footage
Unattended answer file features are about to become better. Guess what will be added with the following screenshot: This is still a work in progress. Only loading items has been implemented
Component settings have been fully integrated now. Also, you can now open your answer files in the Windows SIM and/or edit them with the Editor mode: While system component configuration will not be backported to DISMTools 0.5.1, the latter will
hello thank you for works not multilingual default WinPE sir commandes langues et parametre régionnaux no works
After some additional investigation it appears that attempting to use a portable SSD is/was the issue. I started a new project on a fixed SSD and had no issues. Thanks for your attention to this issue but it was more than likely my own setup and not an actual issue with DISMTools. Once again keep up the great work with this project. It's been invaluable to me.