Windows automatic update for Win10 install - kills BR
Posted: Fri Jan 29, 2016 1:06 pm
Hi all,
Windows 7 and 8 users:
Are you aware that Microsoft is pushing a Windows update to those configured with "automatic updates" to "prepare" for a Windows 10 install? If you aren't aware of it, I suggest that you do a little reading.
My primary client was unable to load BR at all on any of their local workstations this morning because of this update, which came overnight. This had previously happened on ONE workstation which got the update before the others, and we didn't realize what the problem was with BR. We just restored the system to the previous config and it worked again. But then, the update was pushed again overnight - to ALL of their workstations. And then NONE of them worked!
The update creates a hidden folder in the C: root that basically sets up for a Win10 install with the intention (per MS) to remind the customer to install Win10 at some point. It contains the entire Win10 install (6gb) and according to our tech, this new hidden folder contains basically the entire hard drive contents - sort of like a recovery partition or something. It installs some other things too (you can see them online if you google around a bit). We don't know much about it, but once the update was pushed to the workstations, when trying to load BR, we got the error shown in the attached screen capture when BR hit the drive statement. BR couldn't map to the drive (and therefore couldn't find or create wbserver.dat).
If I login to their server via Remote Desktop, I can run BR just fine because I am not running on one of the local workstations with the update. It works fine on my computer in my office too, but I checked and that update is not installed here. (I don't have automatic updates turned on.) If my client restores the computer back to before the update, BR runs fine again. But the update continues to be re-pushed by Microsoft unless you do more to stop it. There are some third party utilities available just for this purpose. I am reading online that a lot of people are pretty unhappy about this.
My client is going to turn off automatic updates on all of the workstations and hide this patch. But this COULD be an issue for the BR community as a whole as this patch rolls out. I don't know why it doesn't play nice with BR.
My drive statement, that it is choking on, is very simple DRIVE L:,L:,L:,\BR
L: is a mapped drive on the server. (which IS accessible through Win Explorer)
They are not running BR client server.
Has anyone else run into this? And if so, do you know why BR chokes? None of their other application software has a problem with it.
-- Susan
Here are a few links of the sources I went to about the unwelcome Windows updates:
http://betanews.com/2015/09/11/remove-u ... ndows-8-x/
http://www.extremetech.com/computing/21 ... load-files
At the end of the following article, it mentions a program that someone wrote to prevent the update from coming back:
http://www.infoworld.com/article/298377 ... 81-pc.html
http://windowsitpro.com/windows-10/reas ... -computers
http://www.computerworld.com/article/29 ... nsent.html
Windows 7 and 8 users:
Are you aware that Microsoft is pushing a Windows update to those configured with "automatic updates" to "prepare" for a Windows 10 install? If you aren't aware of it, I suggest that you do a little reading.
My primary client was unable to load BR at all on any of their local workstations this morning because of this update, which came overnight. This had previously happened on ONE workstation which got the update before the others, and we didn't realize what the problem was with BR. We just restored the system to the previous config and it worked again. But then, the update was pushed again overnight - to ALL of their workstations. And then NONE of them worked!
The update creates a hidden folder in the C: root that basically sets up for a Win10 install with the intention (per MS) to remind the customer to install Win10 at some point. It contains the entire Win10 install (6gb) and according to our tech, this new hidden folder contains basically the entire hard drive contents - sort of like a recovery partition or something. It installs some other things too (you can see them online if you google around a bit). We don't know much about it, but once the update was pushed to the workstations, when trying to load BR, we got the error shown in the attached screen capture when BR hit the drive statement. BR couldn't map to the drive (and therefore couldn't find or create wbserver.dat).
If I login to their server via Remote Desktop, I can run BR just fine because I am not running on one of the local workstations with the update. It works fine on my computer in my office too, but I checked and that update is not installed here. (I don't have automatic updates turned on.) If my client restores the computer back to before the update, BR runs fine again. But the update continues to be re-pushed by Microsoft unless you do more to stop it. There are some third party utilities available just for this purpose. I am reading online that a lot of people are pretty unhappy about this.
My client is going to turn off automatic updates on all of the workstations and hide this patch. But this COULD be an issue for the BR community as a whole as this patch rolls out. I don't know why it doesn't play nice with BR.
My drive statement, that it is choking on, is very simple DRIVE L:,L:,L:,\BR
L: is a mapped drive on the server. (which IS accessible through Win Explorer)
They are not running BR client server.
Has anyone else run into this? And if so, do you know why BR chokes? None of their other application software has a problem with it.
-- Susan
Here are a few links of the sources I went to about the unwelcome Windows updates:
http://betanews.com/2015/09/11/remove-u ... ndows-8-x/
http://www.extremetech.com/computing/21 ... load-files
At the end of the following article, it mentions a program that someone wrote to prevent the update from coming back:
http://www.infoworld.com/article/298377 ... 81-pc.html
http://windowsitpro.com/windows-10/reas ... -computers
http://www.computerworld.com/article/29 ... nsent.html