Error: Folder name not valid (267)
When I use the Windows explorer it opens normally.
After mounting the image in Explorer, can you go to the same path in Opus?
What about in other software (e.g. via the File Open dialogs)?
What is the path it is trying to access?
Did this start happening after Acronis True Image was updated, or Opus was updated, or both?
After mounting the image in Explorer, can you go to the same path in Opus?
No.
What about in other software (e.g. via the File Open dialogs)?
It normally opens.
What is the path it is trying to access?
H:\Kopie van Cantabile Settings
Did this start happening after Acronis True Image was updated, or Opus was updated, or both?
After update to Opus version 12.21
If you right-click the .tib file and open it via the context menu, does that give the same result?
The only change in 12.21 I can think of which might affect this was to some details of what happens on double-clicks.
Right-click gives the same error..
Unfortunately I can only open Acronis .tib files with Windows explorer...
Would it be possible to reinstall 12.20 to verify that it still works with the older version, in case something else changed at the same time?
I've put the 12.20 installer here in case you need it:
If it does work with 12.20, please try then going back to 12.21, in case it was just rebooting or something like that which was the difference.
Let us know what you find, and we'll investigate from there if something in 12.21 definitely looks like the cause.
(In both cases, just reinstall the version over the top of what you have. There is no need to uninstall first, and doing that would wipe your config, which isn't needed to test this.)
Sorry for my late reply Leo...
This version 12.20 does not make any difference! .TIB files are now only accessible in Windows Eplorer. I don't understand what has changed in my system. Perhaps it has something to do with the Windows updates... You'll never know!!
Windows Updates quite often mess around with file types in the registry (even ones that have nothing to do with Windows; it's weird). Maybe repairing/reinstalling True Image would fix the issue, if that's what has happened.