Driver version does not update after software upgrade
10 posts
I upgraded the software to version 25.12, but after 2 reboots the driver version is still 25.8. Is this correct?
Problem solved. I manually updated the driver via Device Manager and the program's target directory. However, I don't believe this is the official solution. I already did this with the last update months ago, which only updated the tool, not the driver. Is it possible to update both the tool and the driver with the new EXE update? As it stands, it's impossible for new users to get the latest version without this workaround.
On a side note, I tried to install the latest version of RAM Disk (4 Jan 2026). It didn't work as planned. I could not even restart my computer after installing this version. I had to restore my entire disk to a previous state because my computer was unusable after that update. :-@
Previous versions of RAM Disk did not cause any problems here, but it is really annoying to be told to restart the computer twice whenever a new build/version is installed.
The old driver version displayed in Windows Device Manager is a purely cosmetic issue: the RAM Disk driver actually gets correctly updated (when it should) after installing a new version, but Windows Device Manager sometimes keeps reporting an older driver version. Updating the driver additionally via Device Manager simply prompts the Device Manager to refresh its display, and thus the problem gets "solved".
We are looking into this issue, and the next release of RAM Disk will offer some improvements in this regard.
@ Buddel
Please provide as much information as possible about this issue, so that we could know exactly what happened in your case. Saying that your computer "was unusable" and you "had to restore the entire disk" is too serious for a "side note". It requires proper investigation.
In the same message, you then say that "it is really annoying to be told to restart the computer twice", which is an enormous leap from an unusable computer. If the problem is real and significant, beyond a mere inconvenience of a reboot, we do need as many details about it as you can provide: screenshots, error messages, precise description of what you saw, etc.
Hi Ann,
Thanks for your message. I will try to install the next (pre-release) build you release. If I run into any difficulties, I will try and add some screenshots and additional info. For the time being, however, I would like to use the current stable version of RAM Disk, which works just fine here. Again, thank you very much for your support.
Thanks for your feedback. But if its only a cosmetic thing, why do I have now the driver version 25.12 in the device manager. Without my manual update the driver version shows 25.8 even after 2 reboots. That means for me, the driver file in the program folder is different to the driver version what is everywhere else stored and used via the installation routine, maybe only in the version number information. Makes no sense for me. Only the manual driver in the program folder would have also the 25.8 version number but this is not the case. But anywhere. All is fine now. It is a little bit confusing and I think an installation/update of such a deep integrated software/device/driver should be more transparent and not leave any questions unanswered about whether everything worked correctly or not. :-)
Drivers are a thing that by its nature is deeply integrated in and managed by the operating system. Apparently Windows can sometimes display a driver version incorrectly in some places, even after the driver itself was successfully updated.
We understand that such version number inconsistency may be puzzling to some users, and we will of course do our out best to fix it if possible. But, as explained above, it is just a cosmetic issue. Our primary focus is on making sure that SoftPerfect RAM Disk is one of the most stable, reliable and fast RAM Disk applications in the world.
Hi Ann, I installed the latest version of RAM Disk, released on 8 January. It was a smooth install - no error messages this time. Best of all, only one restart was required. Well done. Thank you.