Mercy -- I've got it done, and I'm not certain what the main problem was. Some observations:
-- I have two RNDIS ports. To see both of them you have to "Show Hidden Devices" in Device Manager. One had been configured earlier with the IP address required for flashing the AC, but DUMLdore insisted on logging onto the other one for flashing the RC. I configured both RNDIS drivers the same way, and DUMLdore2 loaded/flashed on the next try with no time outs.
-- I was clumsy handling the unzipping of the RC download, and didn't understand what I had where. When the AC bin file is unzipped, you get an application executable along with several helper files, and I had "Loaded" that application file into DUMLdore2 when I flashed the AC. But when the RC bin file is unzipped, all you get are four *.sig files which are not executable. This last time I loaded/flashed the RC, I just pointed DUMLdore2 at the RC bin file to load, and it went right to completion in about 10 minutes.
BTW - Halloweenhamster's comment is right, i.e., the AC does not have to be powered up to connect the PC to the RC. Don't understand with DJI said to do it that way ("Using DJI Assistant" in the Appendix of my V1.6 User Manual).
And both Kilrah and PT_Mavic called it right that the RNDIS config was not right.
THANKS ALL. Maybe this thread will shorten somebody else's journey. Best regards............ R