MakeMKV couldn't find any usable optical drives

[tledford]

I installed an LG WH16NS60 in May or June to my HTPC. Using it, I successfully ripped multiple blu-ray discs and several UHD disc without any issues at all.

A few days ago, I started having STOP errors on this Windows 10 Pro v1903 machine which turned out to be due to bad sectors on the boot SSD so I replaced the SSD and reinstalled Windows 10 using a v1903 USB created using MS' "media creation tool".

No other changes to hardware at all.

On the new install of Windows 10, MakeMKV doesn't see the LG drive and yields the debug log below:
Debug log started at Tue Nov 12 19:07:41 2019 , written by MakeMKV v1.14.5 win(x64-release)
Using 262272KB for read cache.
001005:0000 MakeMKV v1.14.5 win(x64-release) started
001004:0000 Debug logging enabled, log will be saved as C:\Users\xxxx/MakeMKV_log.txt
001003:0020 DEBUG: Code 3221225506 at 2Qm_9E>AR-7CDcy4h=*H:213130582
005042:0000 The program can't find any usable optical drives.
Application exited at Tue Nov 12 19:07:52 2019

Below is the log from the last run on the failing hard drive:
Debug log started at Tue Nov 05 17:50:54 2019 , written by MakeMKV v1.14.5 win(x64-release)
Using 262272KB for read cache.
001005:0000 MakeMKV v1.14.5 win(x64-release) started
001004:0000 Debug logging enabled, log will be saved as C:\Users\xxxx/MakeMKV_log.txt
003338:0000 Downloading latest SDF to C:\Users\xxxx/.MakeMKV ...
003339:0000 Automatic SDF downloading is disabled or failed.
001003:0020 DEBUG: Code 99 at %.rR&vsq2cI<A6cT:29407040
SDF v060: HL-DT-ST_BD-RE__WH16NS60_1.01_211711202000_M61J3P41214
003007:0000 Using direct disc access mode
003338:0000 Downloading latest SDF to C:\Users\xxxx/.MakeMKV ...
003339:0000 Automatic SDF downloading is disabled or failed.
001003:0020 DEBUG: Code 99 at %.rR&vsq2cI<A6cT:29407040
SDF v060: HL-DT-ST_BD-RE__WH16NS60_1.01_211711202000_M61J3P41214
001011:0000 Using LibreDrive mode (v05 id=6E4B09EE276C)
DEBUG: Code 2147483648 at %.rR&vsq2cI<A6cT:213132974
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DISCID=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
003307:0000 File 00001.mpls was added as title #0
003307:0000 File 00003.mpls was added as title #1
003307:0000 File 00004.mpls was added as title #2
003025:0000 Title #00230.m2ts has length of 0 seconds which is less than minimum title length of 1 seconds and was therefore skipped
003307:0000 File 00231.m2ts was added as title #3
003307:0000 File 00295.m2ts was added as title #4
003307:0000 File 00304.m2ts was added as title #5
003307:0000 File 00307.m2ts was added as title #6
005011:0000 Operation successfully completed
005014:0000 Saving 3 titles into directory J:/Video/xxxxxxxx/
004001:0000 Forced subtitles track #4 turned out to be empty and was removed from output file
005005:0080 3 titles saved
005036:0104 Copy complete. 3 titles saved.
Application exited at Tue Nov 05 18:04:14 2019

Other things worth mentioning:
1. Controlled folder access has never been turned on on this machine and is confirmed to be off.
2. I installed the "arbiter service" (can't recall the exact description) as per the defaults.
3. Windows 10 and all other applications see the drive and it functions normally; of everything installed on this new Win10 install, MakeMKV is the only application that doesn't see the drive.

Any ideas?

Regards,
TL

[Woodstock]

Permissions. Microsoft has decided to lock down low-level access to optical disks by default. You can have a working system, do a Windows update, and have a non-working system.

viewtopic.php?f=1&t=20863&p=80884&hilit ... ves#p80884

[tledford]

Thank you, but controlled folder access is off
<<<
1. Controlled folder access has never been turned on on this machine and is confirmed to be off.
>>>

I installed the "CdRom Device Arbiter service" and it is running; however, I have to launch MakeMKV as Administrator and THEN MakeMKV sees the optical drive (thank you for the indirect recommendation). The machine has been rebooted several times since 1.14.5 was installed, so evidently the device arbiter service isn't working as designed (i.e., doesn't allow for running as non-Admin user) on the new Win10v1903 install even though it DID on the previous install of the same Windows version.

What are the special requirements that must be met for the "CdRom Device Arbiter service" to work as designed?