Error Initializing ViGem #42

nwpappas · 2018-02-09T01:16:33Z

Installing with the latest installer, I get a "Error initializing ViGem!" error when trying to run an overlay.

On closing, the screen goes white or black (sometimes one, someone's the other). I can bring up the onscreen keyboard, and move the mouse around, but am blind as to what's going on behind.

Kiviran · 2018-02-20T12:22:52Z

I have the exact same issue.

rusagent · 2018-02-21T00:23:36Z

#metoo. I'm on win 10 pro x64, version 1709, os build 16299.248

sfabris · 2018-03-01T20:11:07Z

#metoo Same here.

benchesh · 2018-03-02T16:54:25Z

Same here. Fortnite isn't getting any of my controller input and the glosc_overlaywindow seems to never close even when I quit the game and the epic launcher

Alia5 · 2018-03-17T20:54:51Z

If you have multiple (or none) "Virtual Gamepad Emulation Bus" devices in your device manager (under System Devices)
Remove them and then run the "Install_Update_ViGEm.ps" script, from the latest Release (v2 or higher), via PowerShell.

nwpappas · 2018-03-17T23:45:47Z

I checked and only had 1 entry. With nothing to lose, I uninstalled and ran script per instructions above, but it didn't fix the problem. I uninstalled and reinstalled (something I'd tried before) and this time it appears to work. On my desktop.

I tried it over the Steam Link and I still get the white screen. No error, but the screen goes opaque when a shotcut is run.

Is the support, or official non-support, for the Steam Link?

Alia5 · 2018-03-18T13:26:29Z

@nwpappas
Good to hear!

Last time I checked, GloSC worked just fine using Steam InHome-Streaming, and therefore with the Steam Link.
However, if the GloSC overlay window is in focus, or the focused window runs in exclusive fullscreen you won't see anything.

AmazingMrBrock · 2018-03-29T15:32:08Z

Hello, been trying is use GloSC but havent been able to yet. I've installed uninstalled installed repeatedly (as admin) and am still getting the vigem error. I have no virtual gamepads in device manager at all, that being the case I ran the vigem updater and rebooted. No dice, full uninstall reboot install reboot install vigem reboot, add game to steam (sea of thieves) reboot, try to start game (inside big picture), vigem error.

It seems like vigem just isn't installing on my system or something.

system is fully updated win 10 x64, steam is up to date but no beta. Glosc is v 2.0.0

Alia5 · 2018-03-30T13:06:17Z

@AmazingMrBrock
You could try installing ViGEm manually (without the script)

https://github.com/nefarius/ViGEm/wiki/Driver-Installation

However, be aware that "Get-ViGEmBusDevice | Remove-ViGEmBusDevice" is currently bugged if you have more than 1 ViGEm device installed. So you have to remove them manually as described above.

AlexanderGalen · 2018-03-31T06:36:48Z

@Alia5
I just want to confirm that I was in the same situation as @AmazingMrBrock, and following the wiki to install ViGEm and then reinstalling GloSC fresh to undo all the other stuff I tried finally got this working for me. Thanks for the help, and thanks for making this in the first place.

If I had to guess why running "Install_Update_ViGEm.ps" didn't work, I'd wager that it's because some of the commands from the ViGEm wiki require administrator privilege, so need to be run from an administrator instance of powershell. When I tried running the script I saw the powershell window pop up and disappear immediately, so I think it may not have privileges and be silently failing. Just some speculation though, I'm no expert.

Alia5 · 2018-03-31T13:35:55Z

The script should restart itself with admin privileges.

heckelson · 2018-03-31T19:33:04Z

Hi, for me (Windows 8) installing ViGEm manually from this link via device manager > add legacy device and rebooting did the trick, the powershell script didn't work for me after running powershell with admin privileges and setting the ExecutionPolicy to Bypass. I installed GloSC via the provided installer and it seems to be working now.

AmazingMrBrock · 2018-04-02T19:15:24Z

That did the trick for me, thanks for the help @Alia5. I also second @AlexanderGalen in thinking its an problem with automated admin privileges not transferring.

FlipEnergy · 2018-04-03T19:11:27Z

Windows 10 here and just installed GloSC 2.0.1.124 and installation went through successfully. However, I looked at your comment above and noticed the virtual GamePad Emulation bus wasn't installed by the script. I tried to manually run it and after it asked for admin privileges, it continues to silently fail and exit immediately. So I ended up just running powershell as admin, copy-pasting the second half portion of the script and ran/installed manually successfully and solved the Error. This is just FYI.

EDIT: I dug a little deeper and found out that the new process simply doesn't run because of this error:
File C:\Users\[me]\dev\GloSC\redist\Install_Update_ViGEm.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170
I'll look to see if we can get around that since most people will have running scripts disabled by default like I did.

Alia5 · 2018-04-04T06:36:25Z

That's interesting!
Thanks!

du-song · 2018-04-05T08:29:44Z

Same issue as @FlipEnergy . Worked around by executing
Set-ExecutionPolicy -ExecutionPolicy Unrestricted
In Windows PowerShell as Administrator

Alia5 · 2018-04-05T11:59:45Z

I'll have it fixed in the next update then.

Thanks all.
Didn't even know that policy "crap" existed >.<

steve1977 · 2018-04-07T12:00:42Z

Facing the same issue. Not clear what the work-around is? I execited the command from @freewizard, but didn't change anything.

Alia5 · 2018-04-15T14:07:32Z

5d00d5c

GloSC-installer.zip

x8009 · 2019-04-16T16:10:34Z

I have issue with

.\Install_Update_ViGEm.ps1
Register-PSRepository : The term 'Register-PSRepository' is not recognized as the name of a cmdlet, function, script
file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At C:\Program Files (x86)\GloSc\redist\Install_Update_ViGEm.ps1:12 char:5

Register-PSRepository -Name nuget.vigem.org -SourceLocation https ...

```
~~~~~~~~~~~~~~~~~~~~~
```
- CategoryInfo : ObjectNotFound: (Register-PSRepository:String) [], CommandNotFoundException
- FullyQualifiedErrorId : CommandNotFoundException

Install-Module : The term 'Install-Module' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At C:\Program Files (x86)\GloSc\redist\Install_Update_ViGEm.ps1:13 char:5

Install-Module ViGEmManagementModule -Repository nuget.vigem.org

And it keeps going with all the other commands.

I am using Windows 10 1809 .

I don't know show to fix this

Alia5 · 2019-04-17T13:17:50Z

Ah, well...
I think ViGEm stopped being available for install via Powershell... I'd have to check that, though.
There will be a plain old setup.exe for ViGEm soon and I'll update GloSC when that drops.

In the meantime, you can try the "Caveman Instructions" (I didn't name them :P)

x8009 · 2019-04-17T15:08:38Z

I've found the issue for me.

for some reason I didn't have files in the powershell modules folder. it's in programs files\windows powershell . but x86 power shell worked but not with the install because it always opened the x64. so I copied all the files from my laptop powershell x64 and it worked fine.

nefarius · 2019-04-18T17:52:40Z

May I alert you fine gentlemen towards the latest and greatest news 😁

x8009 · 2019-04-18T18:23:15Z

May I alert you fine gentlemen towards the latest and greatest news 😁

nice

We just install above / upgrade or we need to uninstall ?

nefarius · 2019-04-18T18:48:26Z

@x8009 just run it and let it do the work 😄

ghost · 2019-05-29T12:59:20Z

Issue still exist, using latest version of Windows 1903, using latest available release of GloSC. Starting ReCore a microsoft UWP game results in getting this error. Please help.
I don't even see that Virtual Gamepad Emulation Bus in my Device Manager.

Dhop84 · 2019-06-13T10:23:54Z

same as @minidarknova

gybandi · 2019-06-19T09:32:30Z

May I alert you fine gentlemen towards the latest and greatest news 😁

Thanks! This finally solved the issue for me ;)

willstefany · 2019-07-13T12:32:40Z

Hi, I get the error and I tried running Install_Update_ViGEm.ps but it opens and closes the powershell right away, I think its getting the is not recognized errors. I am using windows 10 and am trying to get the steam controller to work with forza horizon 4

nefarius · 2019-07-13T19:09:35Z

@willstefany forget the scripts, use the setup I linked.

Alia5 · 2019-10-19T19:03:40Z

latest commits on master use the new installer.
Release: soon(tm)

AlexWayfer · 2020-08-31T19:09:19Z

I have this issue now and nothing helps. I've re-installed GloSC and installed a new version of ViGEmBus. I have no virtual gamepads in Device Manager:

UPD: Resolved by uninstalling and installing a new version of ViGEm, instead of "repair".

cuilean · 2023-07-09T20:24:47Z

I have this issue now and nothing helps. I've re-installed GloSC and installed a new version of ViGEmBus. I have no virtual gamepads in Device Manager:

UPD: Resolved by uninstalling and installing a new version of ViGEm, instead of "repair".

many thanks bro this method worked. honestly the error probably occurred when i DLed glosSi to the D drive but vigem to the C drive unknowingly. i only realized this after i went to reinstall vigem after removing it from PC.

Alia5 mentioned this issue Mar 28, 2018

Instructions for installing on Windows 7? #24

Closed

Alia5 mentioned this issue Apr 4, 2018

not exactly an issue, just need some help with forza #48

Closed

Alia5 closed this as completed Apr 15, 2018

Alia5 reopened this Apr 17, 2019

Alia5 closed this as completed Oct 19, 2019

s1h4d0w mentioned this issue Mar 14, 2022

GloSC_OverlayWindow stays open and messed with subsequent games #151

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error Initializing ViGem #42

Error Initializing ViGem #42

nwpappas commented Feb 9, 2018

Kiviran commented Feb 20, 2018

rusagent commented Feb 21, 2018 •

edited

sfabris commented Mar 1, 2018

benchesh commented Mar 2, 2018

Alia5 commented Mar 17, 2018 •

edited

nwpappas commented Mar 17, 2018

Alia5 commented Mar 18, 2018 •

edited

AmazingMrBrock commented Mar 29, 2018 •

edited

Alia5 commented Mar 30, 2018

AlexanderGalen commented Mar 31, 2018

Alia5 commented Mar 31, 2018

heckelson commented Mar 31, 2018

AmazingMrBrock commented Apr 2, 2018

FlipEnergy commented Apr 3, 2018 •

edited

Alia5 commented Apr 4, 2018

du-song commented Apr 5, 2018

Alia5 commented Apr 5, 2018

steve1977 commented Apr 7, 2018

Alia5 commented Apr 15, 2018 •

edited

x8009 commented Apr 16, 2019

Alia5 commented Apr 17, 2019

x8009 commented Apr 17, 2019

nefarius commented Apr 18, 2019

x8009 commented Apr 18, 2019

nefarius commented Apr 18, 2019

ghost commented May 29, 2019

Dhop84 commented Jun 13, 2019

gybandi commented Jun 19, 2019

willstefany commented Jul 13, 2019

nefarius commented Jul 13, 2019

Alia5 commented Oct 19, 2019

AlexWayfer commented Aug 31, 2020 •

edited

cuilean commented Jul 9, 2023 •

edited

Error Initializing ViGem #42

Error Initializing ViGem #42

Comments

nwpappas commented Feb 9, 2018

Kiviran commented Feb 20, 2018

rusagent commented Feb 21, 2018 • edited

sfabris commented Mar 1, 2018

benchesh commented Mar 2, 2018

Alia5 commented Mar 17, 2018 • edited

nwpappas commented Mar 17, 2018

Alia5 commented Mar 18, 2018 • edited

AmazingMrBrock commented Mar 29, 2018 • edited

Alia5 commented Mar 30, 2018

AlexanderGalen commented Mar 31, 2018

Alia5 commented Mar 31, 2018

heckelson commented Mar 31, 2018

AmazingMrBrock commented Apr 2, 2018

FlipEnergy commented Apr 3, 2018 • edited

Alia5 commented Apr 4, 2018

du-song commented Apr 5, 2018

Alia5 commented Apr 5, 2018

steve1977 commented Apr 7, 2018

Alia5 commented Apr 15, 2018 • edited

x8009 commented Apr 16, 2019

Alia5 commented Apr 17, 2019

x8009 commented Apr 17, 2019

nefarius commented Apr 18, 2019

x8009 commented Apr 18, 2019

nefarius commented Apr 18, 2019

ghost commented May 29, 2019

Dhop84 commented Jun 13, 2019

gybandi commented Jun 19, 2019

willstefany commented Jul 13, 2019

nefarius commented Jul 13, 2019

Alia5 commented Oct 19, 2019

AlexWayfer commented Aug 31, 2020 • edited

cuilean commented Jul 9, 2023 • edited

rusagent commented Feb 21, 2018 •

edited

Alia5 commented Mar 17, 2018 •

edited

Alia5 commented Mar 18, 2018 •

edited

AmazingMrBrock commented Mar 29, 2018 •

edited

FlipEnergy commented Apr 3, 2018 •

edited

Alia5 commented Apr 15, 2018 •

edited

AlexWayfer commented Aug 31, 2020 •

edited

cuilean commented Jul 9, 2023 •

edited