I just wanted to throw this out there and see if any other users are having similar issues. Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files. The odd thing is that it is not happening every time, they go back into the same process and everything works fine. Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week. We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it. It seems like the last update has messed something up, just not sure what yet.
If you have a support contract in place then raise a support incident requesting a patch for ECN-4545, and attach a screen shot of the version dialog displayed after executing "wrun32 -vv".
One Client ended up unionstalling the following windows security patches:
KB4050946, KB4049068, KB4048961, KB4047206. Removal of these stopped our issues with 9107 on work files.
Anther client removed the following:
KB4049068, KB4054521, KB4054518
The common factor was KB4049068 ... but the online description for this update refers to Fijian time zone settings !
I believe what GMCfourX4 suggested is what is actually happening... but I cannot prove it.
I will check if either are using Webroot antivirus
Data Resources Corporation
I am having the same problem, also starting in the middle of December, same symptoms as described here ... 37-07 error when trying to delete a temporary file the process just created. AND, only on a Windows-7 PC accessing a mapped network drive. I am working to have one user remove MS patches that were installed in December, and having another user get the latest MS patches to see if they've fixed the problem. I'll let people know what I find.
I had alerted all of our clients to NOT install the updates and to temporarily cease installing. We have just had one client install all the latest ... they are using MS Endpoint ... and have had no problems since installing last Thursday.
I also saw an article on the web where Symantek had reported 2 MS updates had stuffed them up ...MS actually reversed the updates. I did not record the numbers as they were not in my set of suspects ... theye were earlier numbers. Can anyone else report Symantek Endpoint being involved?