keeps crashing after upgrading to fall creators edition
crashes by trying to save an x64 0 bit file.
Webroot has confirmed they have started rolling out the updated patch release (Version 188.8.131.52). There is no action that you need to take as this update is automatically being deployed.
Here’s what’s in the patch release:
- Fixes issue with file operations after the Windows 10 Fall Creators Update ( typically these are permission issues )
- Resolves an issue where VMWare Workstation (Viewer) 14 displays an error after updating to Windows 10 Fall Creators Update
- Prevent blocking of deletion of sandbox for 3rd party app Sandboxie after updating to Windows 10 Fall Creators Update
26 commentsComments are closed
Webroot Support Confirms:
Version 184.108.40.206 has been released, this build specifically addresses the issues that WSA was having with the Creators update. You're machines should be automatically updating to this build as they check in.
I see a new Webroot build very slowly rolling out to our console. I found an article that seems to indicate the new build
220.127.116.11 is to address problems with Webroot and Windows 10 Fall Creators Update. Have not fully tested yet, but wanted to share.
Latest Update from Webroot:
This is still pending a build release. We currently do not have an ETA, but this is priority number one for our Dev and QA teams. When a build becomes available, machines will automatically update to it. There isn't anything you would need to do on your end.
interpretek South East commented
Until this is patched by either MS or Webroot, I will skip the frustration and use the 365 browser version (https://teams.microsoft.com) I hope that helps some users who either don't have the access or technical comfort level to implement the other workarounds. Its better than those annoying popups and app closing or even worse, not using it at all!
This is killing my productivity !!! I'm an advocate of teams at my company and will stop soon if this is not fixed!
I have the same dialog box...
I have the same issue!
[Deleted User] commented
Fix issue of save dialogue window popping with desktopclientupdate with an x64 file that is empty that then promptly crashes team application!
Brendan A Merritt commented
Hi, I am a Microsoft O365 Concierge. Can you please keep us in the loop as to when a fix is expected?
I have a open case with this issue. They do not seem to be using WebRoot BTW but the symptoms are in fact the same.
I received the following workaround guidance from Webroot Support.
Thank you for reaching out and reporting this issue. First, let us say that we have identified the problem and have a resolution currently being tested by our QA department. It will be scheduled for release soon. Secondly, depending on the nature of the file interaction in place, there are two known methods of working around the issue. Generally, we would recommend you try the first method, and failing that, work towards the later.
Workaround I – Disabling “Check files for threats when written or modified”
There are two different methods to address this issue. If you run agents with an unmanaged policy, please follow the instructions below:
1. Open Webroot SecureAnywhere agent by double clicking the "System Tray" icon at the lower right of your screen or by clicking the "Desktop" icon.
2. Click the "Advanced Settings" button in the upper right corner of the window that appears.
4. Click the "Shields" button on the left side of the options window.
5. Remove the check mark next to “Check files for threats when written or modified.”
6. Click the "Save" button at the bottom of the options window and enter the code when prompted.
If you do not allow for unmanaged polices, you can perform the following steps to create a managed policy that applies the same setting described, and can be applied to specific endpoints in your environment:
1. Sign into the Webroot SecureAnywhere portal
2. Navigate to the Policies tab.
3. Create a custom policy or use one of our recommended policies with the options you wish to have configured and click the "Copy" button near the top of the page.
4. Name and describe your policy, and click the "Create Policy" button.
5. Once the policy is created, double click on its entry to edit.
6. Click the "Realtime Shield" option on the left.
7. Set the Draft changes for "Scan files when written or modified" to "Off."
8. Click the "Save Changes" button and then set "Promote Draft Changes" to "Live."
9. Navigate to the "Group Management" tab and select the endpoints you wish to receive the policy.
10. Click the "Apply Policy to Endpoints" button, select the policy created for this issue, and click "Apply."
11. Once the agents check in, they should receive this new policy and apply it correctly. You can force an endpoint to check for policy changes by right clicking the "System Tray" icon, and selecting "Refresh Configuration."
Note: the application or process will need to be completely restarted for this method to work correctly. The simplest way to achieve this is by rebooting the computer. Once the system comes back up, please test the same actions that caused you to contact us and see if everything works properly. If you are still having issues, please proceed [to entirely disable Webroot as another alternative.]
I ran into this issue. It appears to be from the update functionality. If I click check for updates it will show the dialog box and then crash when you close it.
I don't know if "trying to save an x64 0 bit file" is the *cause* of the problem. It may be a side effect. Whatever the case, it certainly is annoying... and it also did not start impacting me until I received the creators update.
Kevin L commented
The commercial says that this product can make my 10 person team seem like 50 but when their app is crashing, I have a 0 person team!!!!!!!!!
After Falls Creators Update Teams trying to save x64 file and then crashes every half an hour
Patrick Nolan commented
Log file has been uploaded. Thank you for your response, Alex.
Shane van Wyk commented
Same issue here.
Its really annoying as we switched over from using Skype. Its become un-usable because even if you click on cancel when the box pops up, its still closes teams.
Would be awesome to get this problem solved A.S.A.P or have a manual work around to update teams without it crashing, even being able to turn auto-update off temporally.
Patrick Nolan commented
Exact same issue here. I updated to the Fall Creators Update and this began happening. Because I'm an admin and can, I did a clean install of the FCU and this is still an issue. It is rather annoying and it negatively impacts my workflow. If anyone from MS wants to reach out to me, feel free. I will do whatever I can to help resolve this issue.
Same problem here. This happens when it tries to update. Please fix this!
Michael M commented
About every 10 minutes I get prompted to download the file and Teams closes whether I click yes or no.