On 09/18/2019 6:00 AM, Steven Green wrote:
> I've seen errors equally scary, then they disappear after the next 
> windows update.. is it the same context everywhere, is it the same 
> windows update? my guess is yes and yes
> 
> this kind of stuff REALLY scares me.. our network has about six hundred 
> interlocking tables and indexes open all day, with at least two dozen 
> people hitting on everything, constantly.. the reads and writes have to 
> be exact :-)
> 
> 
> -- 
> 
> Steven Green
> Myrtle Beach, South Carolina, USA
> 
> http://www.OasisTradingPost.com
> 
> Collectibles and Memorabilia
> Vintage Lego Sets and Parts
> - and Paradox support, too
> "modridirkac"  wrote in message 
> news:op.z8a0uvb434j8uf@n-jurez.mshome.net...
> 
> I've been geting this error since yesterday on 5 or 6 different
> instalations. (customers).
> They all have in comon, that they have Win server and Win10 workstations.
> 
> Is there something in updates?
> 
> Jure

We have run into this as well. We believe it has to do with SMB1 
protocol, which Microsoft is trying to eliminate. They say it has a 
vulnerability. Here's what we do to fix it:

1. Go to Control Panel-->Programs and Features-->Turn Windows features 
on or off. Look for "SMB 1.0/CIFS File Sharing Support" section and make 
sure "SMB 1.0/CIFS Client is checked. Also, if there is an item in this 
section indicating "...Automatic Removal", uncheck it.
2. Reboot
3. Open a CMD prompt with "Run as Administrator" and enter the following:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb10 start= auto
Each of the above .exe's should return a "SUCCESS". These enable SMB1.
4. We found that sometimes we have to add Exclusions to Defender for all 
folders used by Pdox and our app.

In our experience, not all users on the same LAN will get the "Not exact 
read/write" message. It's very inconsistent. We have applied this fix to 
approx 20 Users out of 400 total.


Hope this helps.
Bob