Prior to today's update, I could mount an image in NTLite and manipulate it outside of NTLite with tools like DISM.
For example, I could mount it and run a bat file like this:
... where %MOUNT% is the NTLite mountpath, and it would show the packages. It now returns "Error 32 ... An initialization error occurred." I triple checked the mountpath. I tried it on multiple wim files, including a stock wim, and I also tried it on two different Windows installations, including a stock installation. Same problem every time.
Likewise, I used to be able to use the app DISM++ to open the NTLite mounted image and make modifications to it. It now reports the mounted image has "an incorrect format". Again, I tried this on two different wims and on two different Windows installs.
According to Google, DISM Error 32 typically means "The process cannot access the file because it is being used by another process."
This was not an issue prior to today's update. And I have no reason to think that the images are corrupt. I can, for example, mount them with DISM++ and manipulate them without any issues. I just can no longer manipulate them when they are mounted with NTLite.
(Yes, my workflow requires making some manipulations outside of NTLite.)
If this is some kind of new feature to protect images while being edited by NTLite, please provide a setting to unlock the image for outside manipulation.
For example, I could mount it and run a bat file like this:
Code:
dism /image:%MOUNT% /Get-ProvisionedAppxPackages... where %MOUNT% is the NTLite mountpath, and it would show the packages. It now returns "Error 32 ... An initialization error occurred." I triple checked the mountpath. I tried it on multiple wim files, including a stock wim, and I also tried it on two different Windows installations, including a stock installation. Same problem every time.
Likewise, I used to be able to use the app DISM++ to open the NTLite mounted image and make modifications to it. It now reports the mounted image has "an incorrect format". Again, I tried this on two different wims and on two different Windows installs.
According to Google, DISM Error 32 typically means "The process cannot access the file because it is being used by another process."
This was not an issue prior to today's update. And I have no reason to think that the images are corrupt. I can, for example, mount them with DISM++ and manipulate them without any issues. I just can no longer manipulate them when they are mounted with NTLite.
(Yes, my workflow requires making some manipulations outside of NTLite.)
If this is some kind of new feature to protect images while being edited by NTLite, please provide a setting to unlock the image for outside manipulation.
Last edited: