Stuart Douglas wrote:Wondering if there has been any movement on this. It seems like MS has washed their hands of the problem, the tech support that I contacted @ MS had narrowed the problem down to a likely bum reference in ECabS. Is someone still pursuing the fix for this?
Do you have your updates for Windows turned on? They released a correction for it in November, https://support.microsoft.com/en-us/hel ... -kb4048955 this one for Windows 10 at least.