- Aug 20, 2017
It seems that changing to 2003/XP avoids the bug. My system is up and running for7 hours, it never ran that long with the original 2016/10 setting. Is there any downside if I change the setting to 2003/XP? If not this can be a sufficient workaround for now...