Our office (windows 10) has been using Rumba 9.1 for around a year and a half. a few days ago some users begun to have issues starting the rumba sessions or even opening the Rumba application. As soon as it's launched both the session and main application close every time. The error log most often shows an issue with faulting application path WdDspPag.exe and Faulting Module Mfc100.dll. We have run some preliminary steps including a clean reinstall, clean boot, and system file checker. Has anyone had any experience with this issue?
#RumbaHi Austin,
Rumba 9.1 was never supported on Windows 10, and is no longer in mainstream support. While 9.1 is eligible for Extended Support, we will not be supporting it on Windows 10.
Hopefully your company has a maintenance and support subscription, you need to consider moving to Rumba 9.5 or 9.5 SP1, both of which are fully supported on Windows 10.
Sorry to be the bearer of bad news,
Tom
Note: The MFC100.dll is part of the MS C runtime libraries, it appears as if something has changed the runtime libraries. Can you check the modified time stamp on the Mfc100.dll? Maybe a re-installation of the VS 2010 C runtime libraries will fix the issue?
Our office (windows 10) has been using Rumba 9.1 for around a year and a half. a few days ago some users begun to have issues starting the rumba sessions or even opening the Rumba application. As soon as it's launched both the session and main application close every time. The error log most often shows an issue with faulting application path WdDspPag.exe and Faulting Module Mfc100.dll. We have run some preliminary steps including a clean reinstall, clean boot, and system file checker. Has anyone had any experience with this issue?
#RumbaHi Austin,
Rumba 9.1 was never supported on Windows 10, and is no longer in mainstream support. While 9.1 is eligible for Extended Support, we will not be supporting it on Windows 10.
Hopefully your company has a maintenance and support subscription, you need to consider moving to Rumba 9.5 or 9.5 SP1, both of which are fully supported on Windows 10.
Sorry to be the bearer of bad news,
Tom
Note: The MFC100.dll is part of the MS C runtime libraries, it appears as if something has changed the runtime libraries. Can you check the modified time stamp on the Mfc100.dll? Maybe a re-installation of the VS 2010 C runtime libraries will fix the issue?
