Jump to content











Photo
- - - - -

Unable to use ImDisk toolkit on Windows Docker containers


  • Please log in to reply
3 replies to this topic

#1 christianexp

christianexp
  • Members
  • 2 posts
  •  
    Spain

Posted 19 August 2020 - 04:27 PM

Hi!

 

I'm having some problems while trying to create a RAM disk using ImDisk inside a Docker container running on WIndows (servercore 1909 version).

 

I am able to install ImDisk through Chocolatey package manager (I am installing both ImDisk Virtual Disk Driver https://chocolatey.org/packages/imdisk and ImDisk Toolkit https://chocolatey.o.../ImDisk-Toolkit), but when I try to create the RAM disk (e.g. with imdisk -a -s 1024M -m X: -p "/fs:ntfs /q /y") I receive the following error:

 

Error loading ImDisk Virtual Disk Driver: Access is denied.

 

I saw the same error were reported and that was recommended to set the startup of ImDisk to System or Manual. I tried it as well, but it doesn't work.

 

Could you give me a hand, please?

 

PS. I am also unable to stop the ImDisk service with "net" command, but I am able to do it with powershell Stop-Service command, which makes thinks weirder.

 

Thanks!



#2 Olof Lagerkvist

Olof Lagerkvist

    Gold Member

  • Developer
  • 1448 posts
  • Location:Borås, Sweden
  •  
    Sweden

Posted 20 August 2020 - 05:06 PM

It is increasingly difficult to use ImDisk for various tasks on recent versions of Windows where something expects a disk volume connected to a physical disk. I would recommend using Arsenal Image Mounter instead. https://arsenalrecon.com/downloads/

There is a command line version available called aim_ll.exe:
https://github.com/A...ne applications

aim_ll.exe has a command line syntax very similar to imdisk.exe, so you
could probably just replace your imdisk.exe command line with aim_ll
without any other changes:
aim_ll -a -s 1024M -m X: -p "/fs:ntfs /q /y"



#3 v77

v77

    Silver Member

  • Team Reboot
  • 602 posts
  •  
    France

Posted 20 August 2020 - 07:59 PM

I wonder if this error is not related to this one:
http://reboot.pro/to...ramdisk-imdisk/

Anyway, it is obvious all that has nothing to do with Windows. There is very likely an antivirus that interfers with permissions and privileges.



#4 christianexp

christianexp
  • Members
  • 2 posts
  •  
    Spain

Posted 21 August 2020 - 02:33 PM

It is increasingly difficult to use ImDisk for various tasks on recent versions of Windows where something expects a disk volume connected to a physical disk. I would recommend using Arsenal Image Mounter instead. https://arsenalrecon.com/downloads/

There is a command line version available called aim_ll.exe:
https://github.com/A...ne applications

aim_ll.exe has a command line syntax very similar to imdisk.exe, so you
could probably just replace your imdisk.exe command line with aim_ll
without any other changes:
aim_ll -a -s 1024M -m X: -p "/fs:ntfs /q /y"

 

I am giving a try to Arsenal Image Mounter. Seems that now the access denied error is gone, but now when I try to generate the RAM disk drive I am getting another error: "The request could not be performed because of an I/O device error". I will keep investigating it and let you know.

 

I wonder if this error is not related to this one:
http://reboot.pro/to...ramdisk-imdisk/

Anyway, it is obvious all that has nothing to do with Windows. There is very likely an antivirus that interfers with permissions and privileges.

 

Mmmm don't think the antivirus is doing tricky things here, as I am disabling it prior to install ImDisk and generate the RAM Disk Drive.


Edited by christianexp, 21 August 2020 - 03:05 PM.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users