Can I integrate uDiscMounter as an underlying engine in my own application?

Yes. You can integrate uDiscMounter into your application, provided that the required copyright notice is included.

To use uDiscMounter and launch or control it from your application, uDiscMounter must be installed on the target system alongside your application.

In the future, we are planning to develop a dedicated developer library called uDiscTools. This library will allow developers to integrate uDiscMounter's disk image mounting capabilities directly into their applications without requiring uDiscMounter itself to be installed on the system. The library can be directly integrated into your application's project.

Learn more: ►uDiscMounter Command-Line Arguments

Why is the number of virtual drives not updated after changing the setting?

See the following article: ►How to add a virtual drive in uDiscMounter

After changing the number of Virtual Drives, you must restart your system for the changes to take effect.

Why is uDiscMounter detected as a virus or malware by Windows Defender?

On Windows 10/11, particularly with recent security updates, Windows Defender or other antivirus software may sometimes detect uDiscMounter as a virus or malware.

This does not necessarily mean that uDiscMounter is actually a virus. The detection may be caused by a false positive due to the way uDiscMounter interacts with the Windows kernel and system drivers. uDiscMounter uses the uDiscTools driver to perform low-level operations such as mounting and ejecting disk image files. These operations require system-level access, which may cause security software to classify uDiscMounter or its associated components as potentially malicious.

If you want to investigate a detection in more detail, you can scan the uDiscMounter executable (.exe) installed on your system using VirusTotal and review the detection results from multiple antivirus engines.

Please note that antivirus detections can vary between security vendors and may change over time. A detection by one or more engines does not, by itself, establish that a file is malicious.