ShareFile DriveMapper Error on Windows 10 startup: The request is not supported

  • 2
  • Problem
  • Updated 7 months ago
  • (Edited)
As soon as I log into Windows, I get this error: "The request is not supported"
The DriveMapper service never launches correctly. Its status (upon hover over the notification tray icon) is "Starting Up"
When I look at the Account Info in Settings, the info is blank.
Also, the Link Expiration Policy is blank.
It feels like authentication wasn't processed correctly, but the error isn't at all helpful in confirming that, nor there's anything else that I could do to fix this.
I tried reinstalling the app a few times, or repairing it...multiple Windows updates occurred since the first time this started to happen.

The result is that I can't use the mapped drives at all.
Photo of Peter Babel

Peter Babel

  • 4 Posts
  • 1 Reply Like
  • frustrated

Posted 9 months ago

  • 2
Photo of Rakesh Kumar

Rakesh Kumar, Employee

  • 19 Posts
  • 4 Reply Likes
@Peter,
Most likely the problem is caused because Windows is preventing DriveMappers file system driver to load. To fix the issue could you please these steps:
1. Look for registry path : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\I/O System

and set key IoBlockLegacyFsFilters to 0.
2. restart windows.
3. restart drive mapper.

For more information please refer: https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/blocking-file-system-filter-drivers
Photo of Peter Babel

Peter Babel

  • 4 Posts
  • 1 Reply Like
@Rakesh, I tried this and wasn't successful. However, I got a new message, once I made the RegEdit changes, restarted the PC and logged out and then logged back into the ShareFile DriveMapper app.
Upon login, I got the first message (The request is not supported) and then I got this one:
"You are not authorized to use this client. Please contact your account admin to enable Drive Mapper"



I've never seen this error before. Only the first one.

Also, all of this started to happen by itself, without me disabling anything. Perhaps after one of the Windows updates.
Photo of Peter Babel

Peter Babel

  • 4 Posts
  • 1 Reply Like
I got it to work!!

I did look at the article you referred me to before, but I missed the part where it says that the new key should be a DWORD type.
I also have to stress that the IoBlockLegacyFsFilters key never existed in my Registry, so I had to create it.

Thank you for showing me the light...
Photo of briped

briped

  • 10 Posts
  • 0 Reply Likes
I had the same issue, which wasn't resolved by adding the mentioned registry value. I had to uninstall the ShareFile PowerShell API before I could get it to work, as well as adding the mentioned registry value (figured this out as I tried removing the value after getting DriverMapper to work, after having uninstalled the API).
Photo of briped

briped

  • 10 Posts
  • 0 Reply Likes
This issues is getting hugely annoying. Every windows update (on inside fast track) for some reason breaks this so I have to do som juggling with restarting / disabling / enabling legacy filters.
Photo of Peter Babel

Peter Babel

  • 4 Posts
  • 1 Reply Like
Yes, very much so...but another restart (after the one with updates) solves it automatically. No need to edit the registries.
Also, every Insider build of Windows 'breaks' Google Drive (now called Backup and Sync) in that it resets everything in it and has me go through login, folder sync setup and such...

Microsoft needs to get their act together...