View Single Post
Old 10-30-2021, 05:40 PM   #16
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,859
Karma: 6120478
Join Date: Nov 2009
Device: many
And what we are trying to tell you is that Sigil has not made any changes that would cause this. Are you even sure that Sigil caused the unknown exception?

Being able to write to one location but not being able to write to another location is caused by something on your file system. It must be some permissions, some security, some anti-virus or something. No one else has reported anything similar on any platform for Sigil 1.7 or Sigil 1.8 or in fact on any earlier version of Sigil.

If it is not permissions/security/defender related, could you have added a Windows file system extension that uses an old version of Qt that kicks in when opening a file browser.

To test for that try rebooting your machine in Safe mode to disable 3rd party extensions, and see if that makes any difference.

Last edited by KevinH; 10-30-2021 at 05:57 PM.
KevinH is offline   Reply With Quote