Windows Defender: Difference between revisions

Latest revision as of 13:02, 21 February 2025

UPDATE: The root cause of the Windows Defender issue has been fully resolved as of February 15th with the release of Fishbowl Advanced 2025.2. The resolution to this issue is twofold:

Windows Defender Update: Microsoft has made changes to Windows Defender that have eliminated the triggering of extended scan times that were causing the delay.
Fishbowl Update: We have released Fishbowl 2025.2 (available as of February 15th), which includes an update to the affected service, JxBrowser. This ensures optimal performance and further prevents potential launch delays caused by Windows Defender scanning the application.

With these fixes in place, the workarounds previously suggested in this article are no longer necessary. If you have been using them up until this point, you can now resume launching the Fishbowl Client normally without any additional steps. If you continue to experience any issues please contact Support as there may be other contributing factors. Thank you for your patience and support.

@@ Line 1: / Line 1: @@
-If your '''Fishbowl Advanced Client''' application is taking longer than usual to launch, it could be a result of a recent change in Windows Defender. Please try the steps below:
+'''UPDATE''': The root cause of the Windows Defender issue has been fully resolved as of '''February 15th''' with the release of Fishbowl Advanced 2025.2. The resolution to this issue is twofold:
+# '''Windows Defender Update''': Microsoft has made changes to Windows Defender that have eliminated the triggering of extended scan times that were causing the delay.
-==Option 1==
+# '''Fishbowl Update''': We have released Fishbowl 2025.2 (available as of February 15th), which includes an update to the affected service, JxBrowser. This ensures optimal performance and further prevents potential launch delays caused by Windows Defender scanning the application.
-# Close the '''Fishbowl Advanced Client'''
+With these fixes in place, the workarounds previously suggested in this article are '''no longer necessary'''. If you have been using them up until this point, you can now resume [[Getting_Started#3._Start_Fishbowl|launching the Fishbowl Client normally]] without any additional steps.
-# In the '''Windows File Explorer''', browse to the following folder: '''C:\Program Files\Fishbowl\client\bin'''
+If you continue to experience any issues please contact Support as there may be other contributing factors. Thank you for your patience and support.
-# Launch the '''Fishbowl Advanced Client''' by double-clicking the '''client.bat file'''<br>[[File:Batch File.png]]
-This should fix the issue, but if not, please proceed to Option 2 below.
-==Option 2==
-# Close the '''Fishbowl Advanced Client'''
-# In the '''Windows File Explorer''', browse to the following folder: '''C:\Program Files\Fishbowl\client\bin'''
-# <u>'''MOVE'''</u> the '''client.properties''' and the '''log4j.properties''' out of the '''bin''' folder and onto to your '''Desktop'''<br>[[File:Properties Files.png]]
-# In the same folder, launch the '''Fishbowl Advanced Client''' using the '''client.bat file'''<br>[[File:Batch File.png]]
-If these workarounds are not effective, please note that the delay typically disappears after Windows Defender completes its inspection of the Fishbowl files. Once this process is complete, no further delays should occur as long as Fishbowl remains open. However, if Fishbowl is closed, the inspection process may restart, causing delays again. We understand that this issue may be causing inconvenience, and we sincerely apologize for any disruption it has caused. Our team is committed to resolving this problem as quickly as possible. Thank you for your patience and continued support.