I usually don't bother with the rare WU that errors out for some reason. However, I'm seeing fairly regular instances now with SCC (I'm running SCC only for now) WUs on all of my crunchers. All are WIN 10 version 1803. The logs show either the finish file present too long message or a message about too many dynamically linked modules attached. One machine that is a crunching-only box usually hangs up with the disk IO light on solid and power-off/on is the only option. This happens every two to three days but tends to occur most often on the cruncher-only box. If I recall correctly, I don't believe I was seeing this prior to the 1803 update but that doesn't mean they are connected. I have about four more months of run time to go on SCC before I reach my goal and switch to another project so I may just do best to wait this one out. One oddity I did notice today in that while all my crunchers are 64bit, not all of the active wu's are running the 64bit science. A few run the 32bit. Again, that may well not be relevant. Mainly, it's the hassle of a cruncher not being seen as reliable after the error wu and all wu's going to PVER for about a day until it's seen as reliable again.