The new release 7.0.19 did the opposite for my system (Windows 10 Pro 22H2 build 19045.6036); after the upgrade, Zotero failed to start its GUI. It only ran as a Windows process.
Re-installation did not help (after killing the process), so I had to downgrade to 7.0.16 and all works fine again.
This is the first time I experienced any issue with Zotero and I work with it on a daily basis.
If so, see Reporting Startup Errors for what we'll need to debug this. If the debug output window doesn't appear either, see Logging to a Terminal Window and copy or take a screenshot of the console window when it freezes.
Debugging mode with error logging was not successful. Zotero hangs and will not write to the console window or fails to create a zotero-debug.txt.
After installing the upgrade today, Zotero did start with a GUI, but it failed to open tabs and hung. I downgraded Zotero and closed all tabs and upgraded again. This time, Zotero started without a GUI (as a background process in Windows). I was unable to capture any error logs.
As the page says, on Windows, you may need to include -console along with -ZoteroDebugText on the command line. There's no way you'd get a GUI (functioning or not) without some debug output.
Upgrade Storage
Re-installation did not help (after killing the process), so I had to downgrade to 7.0.16 and all works fine again.
This is the first time I experienced any issue with Zotero and I work with it on a daily basis.
If so, see Reporting Startup Errors for what we'll need to debug this. If the debug output window doesn't appear either, see Logging to a Terminal Window and copy or take a screenshot of the console window when it freezes.
NB: I start Zotero with profiles to add different libraries from different storage locations I created.
After installing the upgrade today, Zotero did start with a GUI, but it failed to open tabs and hung. I downgraded Zotero and closed all tabs and upgraded again. This time, Zotero started without a GUI (as a background process in Windows). I was unable to capture any error logs.
For now, I am back to version 7.0.16.