"Launch at Windows Startup" not working after upgrade to Windows 11
Status: Inactive
Brought to you by:
w77
Hello!
First of all, thank you for this great piece of software.
I upgraded to Windows 11 in-place from Windows 10 last night. Now, my RAM Disk doesn't get created at start-up anymore. Note that "fast start-up" is disabled.
I tried uninstalling the driver, the toolkit, and reinstalling them, to no avail.
If I go into services.msc and launch the RAM Disk creator service myself, it works fine.
The one workaround I've found so far is to set the startup type to "Automatic (delayed start)" — which does result in the RAM Disk being created, but only after ~2 minutes.
I'm not sure where I might be able to find logs that would help troubleshoot this issue. Please let me know how I might be able to provide any further information.
Thank you.
Did you try to access the drive directly in Explorer and a command prompt by typing the drive letter, for instance "R:"?
Are you using the dynamic memory management? In this case, do you see the RamDyn.exe process in the Task Manager?
It would be surprising, but there could be a new notification issue...
As the service works manually or with a delayed start, I can hardly suspect anything else (such as the antivirus).
1) I tried, and I can't access R: unless the RAM Disk is indeed present in Explorer
2) I have dynamic memory management ticked. RamDyn.exe is not showing up in Task Manager while the drive is missing.
And yeah, my money is on something related to the order of operations between services, seeing as there's two separate ones. Or maybe the problem is that I need to be signed-in (password entered and all)
I installed the toolkit on my laptop (which came with Windows 11) and no issues there.
Both machines' sign-in settings are also identical...
RamDyn works under the "System" account. So it can works without you are logged in.
The only dependency of "ImDisk RamDisk starter" is the driver, and it appears in the properties of the service. So, there should be no issue with the service start order.
This is very frustrating...