Thanks Fred.
I don't understand how privileges would suddenly become an issue. Been running this way for a very long time and the update procedure was exactly as normally used.
Starting the present install as administrator avoids the error message but causes other problems with my QIU setup, which only accesses network drives. So that is not the solution.
Are you suggesting that I should now run the QIU install as admin and then always run QIU as admin? Will this corrupt my current setup?
Regards.
Peter
If you install QU as admin (or even run it once as admin) and then you switch to an account that doesn't have admin rights, there may have been files created by the admin account that cannot be deleted (or written to) by the non-admin account. You should be able to delete the file(s) in question and when the non-admin account recreates them, they should be fine. Did you accept the default install location for the application data? In QU, click "Utilities", "Explore Qimage Application Data". Where does that take you? If it takes you to \programdata\ddisoftware\qimage, then it suggests one of two things:
(1) Your Windows privileges for \programdata are botched: everyone should be able to write to that folder (and subfolders within).
or
(2) You have anti-malware software that is interfering with writing (certain) files to that folder.
Mike
Thank you Mike.
Yes, I did accept the default data location and it is the one you quoted. Upon checking the folder, it is the one that has been used by QI for years and contains all my setups and jobs etc.
As far as I know I had never installed nor run QIU as admin.
If I install and/or start QIU as admin then the error message is not displayed, however QIU no longer recognises network folders according to their assigned letters. This is critical since a lot of saved jobs depend on that letter. The assigned letters are displayed correctly in windows explorer.
It seems that of all the {Q} files it is only the {{Q} Last Start.jst} that is the problem. The others are created and have content.
In the end, QIU became corrupted (hung while creating thumbnails and wouldn't restart) and I had to restore Win 7 from a backup.
Is the "{Q} Last Start.jst" file critical to QIU operation? Could I ignore the error message and proceed as normal?
Thanks again.
Regards
Peter