Greetings,
I just got a new computer which unfortunately came with Windows 11. I had been using Windows 10. I've found that my old manner in modifying VASL extensions doesn't seem to work under Windows 11. The steps I take are:
This may not be a Windows 11 problem but the coincidence is too, well, coincidental.
Any ideas? Need more info from me? Thanks for your help. I'd like to get this solved for obvious reasons.
Al
EDIT: UPDATE; After a deep dive researching this issue I learned the issue was not caused by switching to Windows 11. There was an image in the image folder with an invalid character in the mage file name. The name contained an accented “i” ( í ). I renamed the image, removing the í and the unzip/modify/rezip process worked as expected. The switch to Windows 11 at the time of discovering this issue was purely coincidental.
This thread is available for others to post any other potential Windows 11/VASL issues.
I just got a new computer which unfortunately came with Windows 11. I had been using Windows 10. I've found that my old manner in modifying VASL extensions doesn't seem to work under Windows 11. The steps I take are:
- Decompress the .vmdx file into a folder using 7.zip (I did not rename the file extension, i.e. it remained .vmdx)
- Modify the files in the folder just created.
- Zip the files and the images folder using the "send to" - "compressed (zipped) folder" windows command.
- Rename the file if required and change the extension from .zip to .vmdx
This may not be a Windows 11 problem but the coincidence is too, well, coincidental.
Any ideas? Need more info from me? Thanks for your help. I'd like to get this solved for obvious reasons.
Al
EDIT: UPDATE; After a deep dive researching this issue I learned the issue was not caused by switching to Windows 11. There was an image in the image folder with an invalid character in the mage file name. The name contained an accented “i” ( í ). I renamed the image, removing the í and the unzip/modify/rezip process worked as expected. The switch to Windows 11 at the time of discovering this issue was purely coincidental.
This thread is available for others to post any other potential Windows 11/VASL issues.
Last edited: