Connection failure on fresh windows install

[lolKaizen]

I just reinstalled windows and started to reinstall the driver

Originally it started with giving an issue about the missing vcruntime140.dll

I fixed that by downloading the Microsoft Visual C++ Redistributable

Now all I see is the "failed to connect to driver at 127.0.0.1:23112" prompt

There's no logs or anything in event viewer so I'm assuming I'm missing another dependency. I'm no programmer though so I really don't know

Windows 10 Home

[MolotovCherry]

When there's an error, Windows stops the driver, and you have to manually re-enable it in the Device Manager.

You could try right-clicking and either enable, or disable then re-enable. If the problem was fixed, it should start right up.

You can also download the installer again and run it, try the repair option

Let me know if any of those work for you

[lolKaizen]

Okay so, I reinstalled everything following all the directions in your readme just so I can start fresh, my device manager looks like this.

Disabling and re-enabling does not change anything, it just goes back to looking like the previous screenshots.

After repairing the install, it changes to "Unknown" and dis & re-enabling changes nothing, again.

By the way, it was working yesterday before I reinstalled windows. Same computer, the only difference is that this is a clean windows install

Edit:

Went into the properties and the device status is:
"This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

{Operation Failed}
The requested operation was unsuccessful."

[MolotovCherry]

Okay so, I reinstalled everything following all the directions in your readme just so I can start fresh, my device manager looks like this.

Disabling and re-enabling does not change anything, it just goes back to looking like the previous screenshots.

After repairing the install, it changes to "Unknown" and dis & re-enabling changes nothing, again.

By the way, it was working yesterday before I reinstalled windows. Same computer, the only difference is that this is a clean windows install

Right click on every "Virtual Display" entry you see and "Uninstall device". If you see a checkbox "Attempt to remove the driver for this device", select it too. Also do the same for any "Unknown device" entry you see. Then run the repair again.

If that doesn't work, then run a admin command prompt, type in pnputil /enum-drivers, find any and all entries that will look similar to the following (published name and guid may be different, but the original name and provider name are always the same), note the oem##.inf name, and run command pnputil /delete-driver oem##.inf /uninstall (where ## is the number of the oem.inf file)

In my example below, I'd run pnputil /delete-driver oem21.inf /uninstall

Take care to do this ONLY for the virtualdisplaydriver (you can see it says so under the original name). Leave all other unrelated drivers alone

Published Name:     oem21.inf
Original Name:      virtualdisplaydriver.inf
Provider Name:      Cherry
Class Name:         Display
Class GUID:         {4d36e968-e325-11ce-bfc1-08002be10318}
Class Version:      2.0
Driver Version:     09/26/2023 0.2.2.0
Signer Name:        DriverCertificate

Edit: You are using the latest version of the installer too right? Repairing / uninstalling using the msi should uninstall the driver before reinstalling it, so there should only ever be 1 entry

[lolKaizen]

Hi again, I've done everything you've told me to and still no dice.

I am using the most recent release
virtual-display-driver-0.2.3-x86_64.msi

I did notice that the install and uninstall give me a UAC prompt, but the repair doesn't. I don't know if this is normal or not, but it did catch my eye.

Other than that, I've done everything you suggested and still no luck.

I really appreciate the help.

[MolotovCherry]

Hi again, I've done everything you've told me to and still no dice.

I am using the most recent release virtual-display-driver-0.2.3-x86_64.msi

I did notice that the install and uninstall give me a UAC prompt, but the repair doesn't. I don't know if this is normal or not, but it did catch my eye.

Other than that, I've done everything you suggested and still no luck.

I really appreciate the help.

Could you do a quick check again with pnputil /enum-drivers to make sure there's no drivers virtualdisplaydriver.inf installed anymore? Then uninstall the software completely, and reinstall it?

[lolKaizen]

Just did, still the same thing as before

[MolotovCherry]

Can you double click the driver in device manager and check this window. One of the entries should mention something about not started, or there being a problem. The latest entries are at the bottom of window (the ones with the most recent timestamp). Scroll down in the window and it'll show you a "problem status" with a code

[lolKaizen]

Device ROOT\DISPLAY\0000 had a problem starting.

Driver Name: oem80.inf
Class Guid: {4d36e968-e325-11ce-bfc1-08002be10318}
Service: WUDFRd
Lower Filters:
Upper Filters: IndirectKmd
Problem: 0x1F
Problem Status: 0xC0000001

[MolotovCherry]

Seems 0xC0000001 is just a generic error STATUS_UNSUCCESSFUL sadly. 😥

Please make sure all virtualdisplay drivers are uninstalled again as usual.
Go here and download the "driver" artifact. This is a debug build of the driver. You'll probably get a download warning, this is not surprising since it's not commonly downloaded (it was just built after all)

In the device manager, select any item in the list, then select "add legacy hardware" -> "install hardware that I manually select from a list" -> "show all devices" (hit next) -> "have disk" -> select folder where the inf is -> click "ok" and continue clicking next until it's done, and it'll install it.

Note: This is a debug build, I just want to see if anything changed. This is not a production release, you don't want to keep this driver installed for anything other than this test purpose (so definitely uninstall it after you're done)

[lolKaizen]

Still not working

[MolotovCherry]

Still not working

At this point I'm not exactly sure what's going on. From what I can gather now, it's not related to the driver installation itself or the driver specifically - that goes along just fine - but rather it's something specific with your Windows install and/or system drivers already installed. The generic error doesn't seem related to the driver specifically from what I can tell.

Are all your manufacturer drivers installed/updated? Other than that, I haven't a clue on why. But I can glean the other install was already set up with drivers and everything, and the difference between that one and this one is that this one is fresh.

Edit: Btw, just for informational purposes, driver installation can also be done like so:
In an admin prompt, you can run the following using nefconc

Install

./nefconc --create-device-node --hardware-id Root\VirtualDisplayDriver --class-name Display --class-guid 4d36e968-e325-11ce-bfc1-08002be10318
./nefconc --install-driver --inf-path "path\to\VirtualDisplayDriver.inf"

Uninstall

./nefconc --remove-device-node --hardware-id Root\VirtualDisplayDriver --class-guid 4d36e968-e325-11ce-bfc1-08002be10318

[lolKaizen]

Are all your manufacturer drivers installed/updated?

Yes

But I can glean the other install was already set up with drivers and everything, and the difference between that one and this one is that this one is fresh.

The only real difference is there's no dell bloat on this laptop. I do have all the drivers. The "old" install was pretty similar because this laptop was given as an RMA replacement less than a week ago, and I don't think discord and signal would change anything. Those were literally the only other two things I had installed.

I'll go try to install this on another computer I have. I'll edit this comment with the results in a few mins.

Edit: No issues on other computer, I have concluded that I have a silly laptop

[MolotovCherry]

If you ever find out what caused this on your laptop, please leave a comment again on this issue. (Perhaps I can add it to the FAQ or something). I am truly stumped right now.

I'm going to mark this as closed right now (you did report an issue with crt that I did fix, so thanks for that!). But if you have any other thoughts/concerns/questions, don't hesitate to leave another comment on here (or make another issue if it's a problem). For general discussion (if it's not related to this issue report), you can also make a topic here

If this is somehow still an issue you think is related to the driver, we can re-open this report as well. (Just leave another comment)

I hope you are able to figure out what the root cause was 😢

[lolKaizen]

Hey again, I noticed that you were on windows 11, and so was my other computer. I updated this laptop to windows 11 and uninstalled completely, then reinstalled. Initially it didn't work so I disabled and re-enabled the virtual display in device manager and now it is working. I don't know if this means anything to you but for some reason that solved the problem?

Thanks for all your help again, you really didn't have to spend so much time troubleshooting with me. I really appreciate it

[MolotovCherry]

Hey again, I noticed that you were on windows 11, and so was my other computer. I updated this laptop to windows 11 and uninstalled completely, then reinstalled. Initially it didn't work so I disabled and re-enabled the virtual display in device manager and now it is working. I don't know if this means anything to you but for some reason that solved the problem?

Thanks for all your help again, you really didn't have to spend so much time troubleshooting with me. I really appreciate it

Interesting! I indeed have never actually tested on Win10. I think I have a computer I should be able to try that on. I'll check it out today and see if that's an issue, then report back.

[MolotovCherry]

@lolKaizen Okay, one more test. Does this debug build work? I changed just about the only thing I could think of which might cause a failure.

(Logging is missing in this debug build, but if that was the cause of the failure, it won't cause it to stop working now)

Also, regarding you re-enabling it and it worked, does your computer take more than 5 minutes to boot up? The driver is designed to fail if the computer takes more than 5 minutes to start, but I figured that should easily be plenty of time, so I doubt that's the issue, but I still have to ask. In that specific instance, simply re-enabling it would cause it to work.

Also note: To try out these debug builds, you should always keep the main product installed (just not the driver itself). Uninstalling will delete the regkeys that the driver reads, which is not good. If you uninstalled earlier before trying the debug driver, that would be a reason why it failed.

[MolotovCherry]

Tried it on Win10 and got the same result as you. Will see if I can fix that

[MolotovCherry]

@lolKaizen I believe the Windows 10 support issue should be fixed now. Can you please test for me that it works as intended for you? Here is the debug build for testing

Edit: Well, it should be good anyways, I tested it on the Win10 machine with no problem. I can just mark this as fixed.

Thanks for your report, and enjoy using the driver!

Edit 2: v0.2.4 was just released with the Win10 fix. Feel free to upgrade at your convenience

[lolKaizen]

Hey man, this is awesome. Works perfectly. I appreciate all the work.

Do you have anywhere where I can give you a tip or something? This software helps me a lot and I'd love to give back to you

[MolotovCherry]

Hey man, this is awesome. Works perfectly. I appreciate all the work.

I'm glad it works perfectly on your end now!

Do you have anywhere where I can give you a tip or something? This software helps me a lot and I'd love to give back to you

I do yes. There's a "sponsor" button on my project, which goes through GitHub (or whatever they use). Thank you! I really appreciate that!

[lolKaizen]

Sponsored!