Forced CD eject strange issue with external 4K player/recorder

[hexaae]

WinUAE 4.2.1.
Windows 10 1809 17763.503, external USB BD-RE Verbatim 43888.

Hi Toni, I switched from Verbatim 43890 (Pioneer BDR-UD03) to 43888 (Pioneer BDR-UD04, 4K UHD support) and found a new issue with physical discs (tested Genetic Species and T0 mixed mode CDs)…

The problem: when I boot to WB with WinUAE and then insert a CD, the disc icons will appear on WB dekstop but suddenly Windows will eject the disc with a requester asking me to insert a valid disk in F:\
Curiously, if I insert the disc BEFORE I run WinUAE and then boot my WB, then I'll have no issue (= no unrecognized CD + forced eject) even if I eject/insert the disc from WB multiple times!
The same happens if I start WinUAE in Image Mode, insert the disc from WB, and then switch to real drive F:\ from WinUAE interface: WB will find the disc, display icons and Windows will just notify me of the new disc inside with no forced eject, as expected!

In short: the problem happens only when I boot WB in Automatic/specified F:\ drive mode, and then insert the CD for the first time from Windows desktop or WB. In this case Windows will reject the disk all the time.
If I don't run WinUAE at all of course I'll have no issue with the same disc from Win desktop, never.

This happens even with old WinUAE 2.5.1 so it has nothing to do with recent SCSI changes...

SCSI Log: https://hastebin.com/weruwuxupa.makefile
My cfg: https://gofile.io/?c=feNHOk

[hexaae]

Just upgraded to Win 10 Pro 1903 (18362.116), and the bug disappeared.
I hate Windows

[jotd]

I sometimes have this issue (when inserting CDs/DVDs to rip them in a windows program), and sometimes not. I made the relation with WinUAE after a while. Not systematic. Exiting WinUAE generally solved this.

[hexaae]

Originally Posted by jotd

I sometimes have this issue (when inserting CDs/DVDs to rip them in a windows program), and sometimes not. I made the relation with WinUAE after a while. Not systematic. Exiting WinUAE generally solved this.

Win 10 1903 solved this cd detection conflict. It is (was with 1809 and before) reproducible carefully following the steps above.
It must be a side-effect of CD routines in WinUAE anyway… maybe Toni could improve/rewrite some parts, even if 1903 seems to have fixed it by itself, so don't know if it's worth it.