Windows Defender: Difference between revisions

Revision as of 14:24, 7 February 2025

If your Fishbowl Advanced Client application is taking longer than usual to start, it could be a result of a recent change in Windows Defender. Please try the steps below:

Close the Fishbowl Advanced Client
In the Windows File Explorer, browse to the following folder: C:\Program Files\Fishbowl\client\bin
Please MOVE the client.properties and the log4j.properties out of the bin folder and onto to your Desktop
In the same folder, launch the Fishbowl Advanced Client using the client.bat file
File:Batch File.png

If this workaround is not effective, please note that the latency typically disappears after Windows Defender completes its inspection of 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.

@@ Line 3: / Line 3: @@
 # Close the '''Fishbowl Advanced Client'''
 # In the '''Windows File Explorer''', browse to the following folder: '''C:\Program Files\Fishbowl\client\bin'''
-# If you see any of the following files, please '''MOVE''' the files to your '''Desktop.'''
+# Please <u>'''MOVE'''</u> the '''client.properties''' and the '''log4j.properties''' out of the '''bin''' folder and onto to your '''Desktop'''
-#* <mark>'''install4j.properties'''</mark>
+# In the same folder, launch the '''Fishbowl Advanced Client''' using the '''client.bat file'''<br>[[File:Batch File.png]]
-#* <mark>'''client.properties'''</mark>
-#* '''log4j.properties'''
+If this workaround is not effective, please note that the latency typically disappears after Windows Defender completes its inspection of 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.
-# In the same folder, launch the '''Fishbowl Advanced Client''' using the '''client.batch file'''  If this workaround is not effective, please note that the latency typically disappears after Windows Defender completes its inspection of 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.