Windows Local Disks Losing Share Attribute After Reboot

[mj354]

10 Remote Drives mounted with Raidrive 2025.7.16 version as public local disks lose Windows share attribute after reboot causing issues with subsequent operations.

Trialed similar program Expandrive prior to Raidrive Trial using the same remote drives and Expandrive does not have this problem so the issue is solvable.

If this issue cant be resolved please inform immediately so I can cancel subscription before RaiDrive trial ends.

About Computer

Processor 12th Gen Intel(R) Core™ i9-12900HK (2.50 GHz)
Installed RAM 64.0 GB (63.7 GB usable)
System type 64-bit operating system, x64-based processor
Edition Windows 11 Pro
Version 24H2
Installed on 5/29/2025
OS build 26100.4946
Experience Windows Feature Experience Pack 1000.26100.197.0

[RaiDrive]

Hi, @mj354

The Windows lanmanserver service does not share paths it cannot find.
For example, if you share the X: drive and reboot, if the X: drive doesn’t exist when lanmanserver starts, the sharing won’t start.
This is because the RaiDrive service starts last, and drive mapping occurs afterward.

Even if you connect the X: drive later, lanmanserver won’t recognize it and the sharing won’t occur.
One simple and straightforward solution is to restart the lanmanserver service.

• After connecting the drive, run CMD with administrator privileges and execute the following commands:

net stop lanmanserver
net start lanmanserver

Be careful, as other users may already be using shared files or printers.

Restarting lanmanserver will immediately share the registered shares and ensure they work properly.

We could restart the lanmanserver service after connecting the drive, but this is a very risky approach.
This is because files or printers may already be in use from a shared location on another drive.

We could also automatically remove and register shares, but we found this difficult to reflect the diverse settings and purposes of users.

We’re still researching and considering this, but stability and other considerations make it difficult to make a decision.

We apologize for not being able to provide a definitive solution. If you have any suggestions, please let us know.

Thank you,
RaiDrive Support

[mj354]

@RaiDrive

files or printers may already be in use from a shared location on another drive.

Thanks for replying. I’m not a programmer so I can’t provide any technical suggestions. But my thought would be to create a script or process that could delay the lanmanserver startup during reboot until after the RaiDrive starts and connects all the drives. I’m sure you’ve probably thought of this already though. From testing on my local network, even if files or printers may already be in use from a shared location on another drive, they will only momentarily indicate a conflict due to the share being unavailable. Once the share comes back online, the files are re-registered as available without any data loss.

In my case, I have 12 remote drives that are shared locally and if they are not available and shared immediately after reboot, my search application will fail to recognize them and remove them from the index. So, after every reboot I would have to manually re-add 12 drives and parameters back into the search application, manually re-share the volumes in Windows, and wait a significant amount of time for 12 15tb drives to be re-indexed - EVERYTIME. This is obviously untenable which would be a shame since most of the other functions on RaiDrive seem to work ok so far.

Important note: The first time I rebooted after setting up RaiDrive volumes I noticed all of the drives needed to be re-shared. I wasn’t sure what was causing the issue so I re-added the search parameters and share setup and rebooted again. After this second reboot, I noticed that only half of the volumes lost the share property. This is still very bad but better than all of them being lost. But it also doesn’t make sense that some drives kept the share properties and others didn’t. Based on your explaination of the problem, they should all be failing or surviving together. This seems to be an area for investigation since it indicates that it is possible for RaiDrive to properly keep the share property after reboot.

After reviewing the support forum, it seems this is a known issue for some time. Regardless of the other good working functions of RaiDrive, not having a core feature work properly for a paid program is very bad.

I’ll attach all the RaiDrive logs separately to the support link for you to review.

[RaiDrive]

Hi, @mj354

We’ve emailed you a version that adds the ability to restart LanmanServer.
If you’ve tested it, please let us know the results via email or on the forum.

RaiDrive Support

[mj354]

Sorry for the late reply. You initially told me someone would work on it in a week or two so I didnt check back sooner to see your early response.

I have done multiple restarts/shutdown-restarts to see if RaiDrive can now maintain the Local drive connections and it seems to be working using the modified RaiDrive version you sent. There are one or two drives that seem to lag behind the others to get reconnected after shutdown/restart, but if you wait 5-10 seconds before entering your pswd on the login screen to provide time for everything to get situated, all drives will be back up and ready for use.

The options utilized are:

-The drives set to public + local
-Windows share must already be registered.
-Reconnect at boot is enabled.

Thank you for making this modification to RAiDrive.

[RaiDrive]

Hi, @mj354

Thank you for letting us know the results.
I’m glad to hear it works.
This feature will be reflected in the policy.

If you connect with Public + Not Local (network), the entire drive is shared properly.
I’d like to know why you’re using Public + Local.
Is it because you want to share subfolders?
If you could tell us the reason, it would be helpful for RaiDrive’s policy.

RaiDrive Support

[mj354]

Hi,

Just to confirm we’re on the same page, here are all my settings:

I’d like to know why you’re using Public + Local.
Is it because you want to share subfolders?

Yes. I used Public + Local to enable other PCs on my local network to have instant access to all the shared remote drives including subfolders without me having to map new network links separately on each computer.

I based this on the info from

Local Disk - RaiDrive GUI

Tip
You can set up a combination of Public/Private and Local Disk/Network Drive.

Public : Access from another account or PC
Local Disk : Recommended for using Radarr app

If this can be set up in a better way to achive the same goal please let me know.

*Also, although the Local drives are being re-connected automatically now, there is still an issue with EverythingSearch whereby all remote drives still need to be re-indexed after restart which is not the normal behavior (if using network links). I think it is due to the drives being totally disconnected by RaiDrive prior to restart which is indicating to ES that a re-index is necessary. I’m working with ES forum to get to the bottom of it and determine if something needs to be done by ES or if a slight mod to RaiDrive reconnect process would fix the issue.

I’ll repost when i have more info.

[RaiDrive]

Thank you for the information.

If you want to share differently by folder or user, you should use Public + Local.

We’re in a very difficult situation with indexing or search programs like EveryThing or FreeFileSync.

RaiDrive doesn’t store existing file/folder information locally when the drive is disconnected.

We could store file/folder information locally, but when the drive is reconnected, we’d have to find and reconcile the differences between the remote and saved information.
This would ultimately require retrieving all remote information.
This comparison would defeat the purpose of storing the information locally.

Therefore, when the drive is disconnected and reconnected, the file/folder information is gone, so it must be re-fetched from the remote location when a list is requested.

When RaiDrive connects a drive, a new drive ID is automatically assigned internally (due to the internal operation of the virtual file system), and this is recognized as a new drive by both the internal and remote PCs.

When you start a search in EveryThing, it searches all subfolders, and RaiDrive must retrieve the list information for all requested folders remotely.
If you disconnect and reconnect the drive, it must retrieve the information remotely again.
This is a very time-consuming operation.

EveryThing’s requests make numerous requests to the remote server, which can lead to request limits.
Most popular storage providers (Google, OneDrive, etc.) have request limits, so excessive requests can lead to request limits, which ultimately delays all operations.

When an app requests a list, even if the list has already been retrieved, changes may exist remotely, so it must re-retrieve the list and compare it before returning it.
Therefore, unnecessary list requests increase the load and only lead to more unnecessary requests.

For this reason, it seems undesirable for other users using network sharing to use EveryThing.

After connecting the drive to the main PC where RaiDrive is running, you can quickly access it remotely after using EveryThing once, so we recommend using it only on the main PC.

If you have any comments or suggestions regarding this, please let us know.

Thank you,
RaiDrive Support