Repository navigation
Nightly Upgrade VDD Error on Install #660
Description
Bug Symptoms
When upgrading to 2.0.2-nightly.d20261022.83bb31680419 the installer says "installed with error virtual display driver could not be installed". The installer will hang. Vibepollo looks functional, but when play a game like Forza Horizon 6 the game says the window is losing focus when using the VDD. The VP UI shows that the VDD is actually installed, but using the driver is very buggy.
Expected Behavior
Install would complete successfully without error, and playing with a VDD would work like it did on previous versions.
Windows Version
25H2
Package
Windows - exe installer
GPU Type
NVIDIA
GPU Model
RTX 4090
GPU Driver Version
Latest one for Modern Warfare 4
Capture Method
Windows.Graphics.Capture (Windows)
Apps
Logs (Optional but Recommended)
The export logs button is not working for me and the logs the installer save to my desktop are 16.8 gb and 283 mb compressed (which seems like quite a problem) so I cannot upload them either.
Screenshot (Optional)
Activity
Nonary commentedon Oct 23, 2026
Thanks for reporting this. Please don't upload the 16.8 GB report or delete/reinstall the driver yet.
Could you tell us:
If you can open the newest individual installer log, please share only its last 100–200 lines and a short excerpt around VIRTUAL_DISPLAY_DRIVER_WARNING or VIRTUAL_DISPLAY_RESTART_REQUIRED. Redact usernames and personal paths. If you can't locate that log, just answer the three questions first.
The driver payload itself is unchanged from the previous published nightly, but the installer's retained-driver checks changed. We're investigating those checks; we haven't established that they caused your failure. We'll keep the game-focus symptom separate for now.
DABnoREGRET commentedon Oct 23, 2026
Same problem as well, here's a log file for you to check
vibeshine-install-warnings-20261023_094838.txt
Nonary commentedon Oct 23, 2026
@DABnoREGRET Thanks, this log is enough to identify your installer warning. Both display-driver checks hit the initial 15-second inventory timeout on 2.0.2-nightly.d20261022.83bb31680419, so driver updates were skipped even though the application installation completed successfully.
The initial inventory optimization is already in Vibeshine canary, but is not in the published Vibepollo nightly yet. It avoids enumerating Windows inbox drivers unnecessarily while retaining the timeout and safety checks. No larger log upload is needed for this warning. This does not yet establish the cause of the original report's game-focus or log-export symptoms.
vitorhugoaranda commentedon Oct 23, 2026
log of 3 differents computers:
vibeshine-install-warnings-20261023_005526.txt
vibeshine-install-warnings-20261023_005637.txt
vibeshine-install-warnings-20261023_005759.txt
vibeshine-install-warnings-20261023_010004.txt
fix(installer): bound retained display inventory queries
Nonary commentedon Oct 23, 2026
@vitorhugoaranda I checked all four files. They consistently show the initial 15-second inventory timeout for both display drivers on 2.0.2-nightly.d20261022.83bb31680419; the application MSI itself completes successfully. No more logs are needed for those warnings.
The inventory optimization has now been migrated into Vibepollo source, alongside separate hardening for the later retained-driver checks. It is not in a published download yet. We'll follow up with the containing nightly for a retest. The separate USB/IP controller notice in one report is not the same display-driver warning.
anilkusaksiz commentedon Oct 23, 2026
Received a similar error on my end, is the root cause the same?
Logs:
vibeshine-install-warnings-20261023_103827.txt
Nonary commentedon Oct 23, 2026
The containing build is now available: 2.0.2-nightly.d20261023.8a753af16dcf. It includes the initial driver-inventory optimization and separate timeout hardening for retained-driver checks.
@anilkusaksiz I checked your attachment too. It records the older October 22 build, the same initial 15-second inventory timeout for both display drivers, and successful MSI completion. No additional logs are needed for that warning.
Please try the new installer and confirm whether those warnings are gone. For the original report, please also tell us separately whether installation completes normally and whether the focus/log-export symptoms remain. Those symptoms have not been established as the same bug, so this issue is staying open for confirmation.
anilkusaksiz commentedon Oct 23, 2026
Installed that version and saw errors again, attaching the logs:
vibeshine-install-warnings-20261023_115940.txt
davetappy commentedon Oct 23, 2026
i'm having similar issue
vibeshine-install-warnings-20261023_134440.txt
Nonary commentedon Oct 23, 2026
@anilkusaksiz Your new log confirms this still happens on 2.0.2-nightly.d20261023.8a753af16dcf: both initial driver inventories exceed 15 seconds, while the application MSI completes successfully. These are current warnings, not leftover logs from the previous build. Removing -All was not sufficient on your machine, so this remains unresolved.
I'm checking the remaining inventory work rather than asking you to reinstall drivers manually. @davetappy I'm checking your attachment separately before assuming it has the same cause.
Nonary commentedon Oct 23, 2026
@davetappy Your log shows a different warning: Sunshine's safety check rejects the reported driver version "1.4.4." because it is incomplete. It does not hit the 15-second timeout. SudoVDA is retained successfully, and the application installation completes.
The same version warning also appears in the older installs in your log. We should not guess the missing version component or remove the safety check. The current message does not identify which inventory source supplied that value, so that needs to be made explicit in the installer diagnostics.
Nonary commentedon Oct 24, 2026
@anilkusaksiz and anyone still seeing the initial inventory timeout: 2.0.2-nightly.d20261024.df3b45b4df14 is now available. It adds one bounded recovery attempt after the initial timeout. This is a recovery mitigation, not confirmation that we identified the underlying Windows provider slowdown.
Please try its Windows installer and confirm whether the display-driver timeout warnings are gone and installation completes. Allow a few minutes for the driver checks if recovery is needed. There is no need to manually remove drivers or upload a full diagnostic archive for this retest.
The incomplete-version warning reported by @davetappy and the original focus/log-export symptoms remain separate. This issue stays open pending confirmation.
GotTheShakes commentedon Oct 25, 2026
I tried the latest nightly and while the installer finished without warnings, I'm still seeing the issue with games reporting the window is losing focus. The last working nightly for me in that regards is the 10/18 build. I'm going to go back to 2.01 stable to see if that is working correctly, but I seem to remember it was.
Nonary commentedon Oct 27, 2026
I did find a bug in the autofocus code which was fixed last night, might be working now
anilkusaksiz commentedon Oct 27, 2026
Installed 2.0.2-nightly.d20261026.r.1.e3d13d104c0b without any issues
GotTheShakes commentedon Oct 29, 2026
I installed the latest nightly 2.0.2-nightly.d20261029.r.1.a8ef56b07f39 and have been messing with Forza Horizon 6 for about the last 20 minutes and I haven't seen it auto pause the game becaus of losing window focus so I would say this does seem like it's fixed.
Nonary commentedon Nov 1, 2026
Thanks for confirming that installation now completes without warnings and the focus/auto-pause problem appears fixed on the October 29 nightly. Closing this as resolved. If either problem returns, or log export still fails, please reopen this issue with your version and updated details.