RDSS MAJOR problems (resolved pending update)

[Ted Craven]

Folks, as of sometime this morning Monday February 19, 2018 - Several RDSS 2.1 users are reporting significant problems with all kinds of normal operations of RDSS.

The symptoms are simply - the 'non responding' message in the program header and the little 'wheel' spinning indicating that something is happening. This happens so frequently - for example in moving between Tabs, or selecting pacelines, even doing Downloads in the Data Centre - that RDSS V2.1.045 (and I suspect many other RDSS Versions) effectively grinds to a halt.

This appears to be related to specific Windows 10 versions, specifically so far - Windows 10 Version 1709, Build # 16299.xxx where xxx is a further 3 digit sub-build number which varies. I don't know if the problem is the 1709 update version, or the 16299 Build version, or what

While I drop everything to investigate this - could I please ask everyone who sees this and is having this problem to please post here (or send me by email) your current Windows 10 Version info. Here's how to find that.

Use the Search bar to type the program winver. This displays the Windows Version which looks like this (on my computer). We're interested in the red highlighted version info:



My Windows version info is an earlier version than the one which several folks have reported using while experiencing the RDSS problem.

I am trying to find out which Windows Versions are responsible for the problem, and THEN try to find out how to solve the problem after doing some research.

I would be VERY interested in knowing if anyone using the older RDSS 2.0 also has the problem on Windows 10 Version 1709.

In the meanwhile, I can suggest that people try to roll back their Windows 10 Updates to a previous version to see if that solves the problem, and if so - WHICH version is still stable for RDSS. If you get a satisfactory solution, please report here (or by email to me) what eventually worked for you, with as much detail as possible - thank you!

Sorry about this latest problem. I am now working with a few people to do some testing with this system roll back attempt to (temporarily) correct things.

Please stay tuned.

Ted