I haven't had any issues with this update rolling out in my environment pretty widely, even on non-Windows 10 machines. I don't expect to really have any issues either since "the bug" will be in the next general release. However, it does appear to be rolling out automatically regardless of O/S.
In my agent spread, I'm about 50/50 between X.34, and X.44 - some of that is my own doing, but it appears to be rolling out automatically across the board. Just an observation.
The issue didn't involve WSA changing file or folder permissions - WSA was locking the file / folder and hence other processes couldn't access it for activities such as deletion / moving etc...
Once the fix was applied or WSA was removed, the issue was resolved.
This put me through a significant amount of heartburn this morning after the Windows 10 Fall Creators Update installed. I'm glad that this patch is available but I had a difficult time tracing this issue back to Webroot. Originally I assumed something had gone horribly wrong with the Windows update because I was getting permission denied messages in multiple apps and VMware refused to start any VMs and nothing pointed directly to Webroot.
This is such a major compatibility issue that Webroot should have been far more proactive in alerting customers to this problem. The issue has been known for two months, has serious adverse effects, and yet Webroot didn't push this fix out to the endpoints or even alert its customers via e-mail? I find this to be extremely troubling.
I urge Webroot to do a much better job in the future of being proactive with its communications on issues like this rather than burying the info within community forums.
100% agree with you, I have just sorted another one out after our customer was back and forth to their 3rd party software vendor for two weeks, it finally dropped on my desk and got fixed.
now I need to answer diffulicult questions from a major customer... what do I tell them, its webroot's fault here is their number, but good luck at getting an answer or a patch for a known problem they fixed months ago!!
I have just encountered an issue with Windows 10 Fall Creator that is somewhat related to this thread hence my post, I would like some feedback before making any assumptions or spending too much more time on it.
On a fresh install of Windows 10 Fall Creator that has NOT had webroot installed.
Then attempting to install Webroot is unsuccessful.
What I am finding is that you instigate the installation from the wsainstall.exe and nothing happens.
Checked processes, nothing. Checked event viewer, nothing.
Can anyone provide any feedback to this?