>A recent Windows update of some sort does seem to be the culprit. Worked fine right after the OS install (3rd machine in a row). After doing the Windows updates, the error started happening.
>
>Setting it readonly on the server, as suggested by Ric, is my workaround.

I'm glad that you got a workaround.