cancel
Showing results for 
Search instead for 
Did you mean: 

Windows 10 Fall Creator Update - Bug Fix

Administrator

Windows 10 Fall Creator Update - Bug Fix

After updating to Windows 10 Fall Creators, users may get notified that access to files and or folders was denied.  Typically, this will happen when creating, updating, moving or deleting existing files and folders.   

 

We’ve identified the root cause and have created a patched version of WSA that is currently undergoing QA testing.   Once all testing is complete, the patched version of WSA will be made available to our customers for manual and automated installations using GSM.  We are closely monitoring the inflow of support calls and may push the patched WSA to all customers if the need arises. 

 

The next version of WSA, due around December this year, will have the fix included and customers will receive it then as part of the normal deployment processes.

 

There are two workarounds that can be used until the patch version is available.

 

Workaround 1 – If you run agents with an unmanged policy, perform the following on each device

  • Open the Webroot SecureAnywhere agent by double clicking the System Tray icon in the lower right of your screen or by using the desktop icon.
  • Click the Advanced Settings button in the upper right of the window that appears
  • Click the Shields button on the left side of the options window
  • Remove the check mark next to “Check files for threats when written or modified”
  • Click the Save button at the bottom of the options window and enter the code when prompted

 

Workaround 2 – If you run agents with other policies, perform the following steps

  • Sign into the Webroot SecureAnywhere portal by visiting http://my.webrootanywhere.com
  • Navigate to the Policies tab and select the policy used by your agents
  • Click the Realtime Shield option on the left
  • Set the Draft changes for ‘Scan files when written or modified’ to Off
  • Click the Save Changes button, then the Promote Draft Changes to Live button
  • Once the agents check in, they should receive this new policy and apply it correctly.

 

In both cases, note that the application or process that reported the error will need to be completely restarted. The simplest way to achieve this is by rebooting the computer.

 

Key points

  • Only Windows 10 with Fall Creators update installed are impacted
  • The issue does not affect all Windows 10 with Fall Creators update installed
  • Workaround is available
  • Patched version of WSA is on the way
  • Patch available for manual or automate installations using GSM
  • Fix will also appear in next release of WSA , due December this year

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Anna - Webroot Sr. Advocate Programs Manager
17 REPLIES
Community Manager
Soccer
Webroot

Re: Windows 10 Fall Creator Update - Bug Fix

UPDATE!

 

We’ve been working on a patch and wanted to update you with the latest information about this. The patch release is ready.

 

WSA 9.0.18.44 patch release is available for the following issues that have been reported by customers who have updated to Windows 10 Fall Creators 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

 

There are various mechanisms available to fix these issues and affected devices manually. For example:

 

 

Key points

  • Only Windows 10 with Fall Creators update installed are impacted
  • The issue does not affect all Windows 10 with Fall Creators update installed
  • Workaround is available
  • Patched version of WSA is complete
  • Patch available for manual or automate installations using GSM
  • Fix will also appear in next release of WSA , due later this year

 

If you’re still experiencing problems, please contact Customer Support as they will be able to assist you further.

 

Thank you!

 

------------------------------------------------------------
Drew - Community and Advocacy Manager
Member

Re: Windows 10 Fall Creator Update - Bug Fix

Hi,

 

Will this update get applied automagically to all deployed systems in the consol?

 

Thanks

 

Administrator Administrator
Administrator
Music
Nature

Re: Windows 10 Fall Creator Update - Bug Fix

@GigaTech, no, you will need to follow the steps in the post above. The reason why we haven't pushed it out fully is because it's a patch release and should only be applied to impacted devices (i.e. Windows 10).

New Member

Re: Windows 10 Fall Creator Update - Bug Fix

Hi,

 

When can we accpect this to be solved in an automatic update?

Now we have to wait for the customer to be affected and then solve it, not a good solution for relationship we the costumer.

Or heavely reduse the protection whith the workaround i the policy.

 

Regards

Anders 

Member

Re: Windows 10 Fall Creator Update - Bug Fix

I agree with the above comment... this should be auto deployed via auto updates

 

It took me a week to add 2 + 2 = webroot, I thought it was my 'dodgy' system and only found out by rebuilding it and all was fine till webroot was installed...

 

So who else/how many people are thinking it is their dodgy system and not dodgy antivirus software?

Moderator

Re: Windows 10 Fall Creator Update - Bug Fix

The fix is in the next full release of WSA and that will be autodeployed.  For the moment, you will need to use the console to deploy and we would advise you do so only to impacted devices i.e Windows 10.  

 

If you have any scripting tools, then these can also be used to deploy the update.  

 

Next full release is due later this year / very early Q1 2018.  

 

 

Regards,

 

Jonathan

 

Frequent Voice

Re: Windows 10 Fall Creator Update - Bug Fix

Can someone provide clarification on these statements with regard to the bugfix?

 

Key points

  • Only Windows 10 with Fall Creators update installed are impacted
  • The issue does not affect all Windows 10 with Fall Creators update installed
Community Guide

Re: Windows 10 Fall Creator Update - Bug Fix


JGiffard wrote:

The fix is in the next full release of WSA and that will be autodeployed.  For the moment, you will need to use the console to deploy and we would advise you do so only to impacted devices i.e Windows 10.  

 

If you have any scripting tools, then these can also be used to deploy the update.  

 

Next full release is due later this year / very early Q1 2018.  

 

 

Regards,

 

Jonathan

 


Interesting.  I've just had a couple of newly onboarded systems show up as having the .44 client, and I have done nothing special (our other techs deployed the antivirus, and I've issued no documentation about .44 yet within our company).  Could .44 be deploying by accident?


We are SysAdmins.
We walk in the wiring closets no others will enter.
We stand on the bridge, and no malware may pass.
We engage in tech support, we do not retreat.
We live for the LAN. We die for the LAN.

New Voice

Re: Windows 10 Fall Creator Update - Bug Fix

What I can't see here is a fix for files that have been screwed up.  I'm assuming the fix below will stop Webroot from borking permissions on future files but what about broken files?  None of the standard processes (i.e. take ownership, etc.) work to regain access to these files and folders.  And they've replicated to other computers as they existed in my OneDrive folder so the problem exists for me on computers that don't have Webroot (switched to other AV solution months ago).