Skip to main content
Up and Coming
October 25, 2014

Interfering software is preventing the Rift from activating

I'm trying to run the Demo Scene in the utility with the Rift Display Mode set to Direct HMD Access.
Running Windows 8.1.
Rift Firmware 2.12
Rift Runtime 4.3

Error:
There is a problem with your Rift configuration.
Interfering software is preventing the Rift from activating. Loaded UMD is reported as 'nvwgf2um.dll'.

Anyone else?

    48 replies

    New Participant
    December 21, 2014
    I had this problem with nvwgf2um.dll interfering, I have a 590GTX, windows 7, 2 monitors and the OR.
    I could solve my issue but I had to unplug my second monitor, plug the OR into the first DVI slot, and my main monitor into the 2nd DVI slot.
    nvidia control panel > configure multi GPU, Surround, PhysX > enable Maximize 3D performance / and auto-select processor

    I hope this works for some of you, now Im going to try to plug my second monitor back in and Ill keep you updated if I find a solution...
    Up and Coming
    January 1, 2015
    Ugh... So I did a clean install of windows 8.1 recently, rolled 344 nvidia driver on and boom...this issue pops up. Direct mode throws the DLL error on any application launch including ipd calibration and oculus demo. Extended mode activates rift but apps only display on projector. Tried belagio app without success. I'll try moving monitors around and see if that helps...

    THIS is why Gear VR is so attractive!

    8.1 with classic shell
    Intel z77 mb
    2-970's SLI disabled
    Acer projector on primary HDMI, rift on DVI on same card.
    New Participant
    February 4, 2015
    I have the same problem (nvwgf2um.dll). I have 2xNvidia Quadro graphics cards installed, SLI disabled. The Nvidia control panel recognizes the rift, and extended mode works, but direct mode crashes with this interfering software message. I only have one monitor attached, plugged into the second card.
    Inspiring
    February 5, 2015
    It's probably SLI. Unfortunately, disabling SLI is not enough. You may have to remove the card (or disable the PCI slot in the BIOS). This is super-inconvenient, I know, so better to use extended mode if you can.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    New Participant
    March 10, 2015
    I had this problem today with NVidia GeForce GTX 570 with two monitors connected via DVI.
    Disconnecting one of them so I have 1 monitor and Oculus connected solved.
    New Participant
    March 17, 2015
    I have exactly the same problem. I have an Nvidia GeForce GTX 560 Ti.
    Unplugging the second monitor does solve the problem, but plugging it back re-introduces the problem unlike 'jcollins' above who suggested that it seemed to work.

    Not sure how to work without a second monitor.
    Is there a solution in progress?
    Inspiring
    March 17, 2015
    What is the model of the second monitor you have and what video ports are you using?
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    New Participant
    March 22, 2015
    I'm getting this problem in the latest build of windows 10 (Build 10041).

    I have been checking around device manager and it looks like the .inf for the display driver in the rift drivers directory is attempting to attach to it but I can't get it to load any driver other than the generic PNP monitor driver.

    I don't have a non windows 10 device around to test if the drivers normally load for the DK2 display, but I figured this might be helpful.

    Also: It prevents the Elite Dangerous launcher from loading, so that's a bummer. It's better than what the previous build of win10 was doing (not displaying a start bar), so at least I have that going for me.
    New Participant
    March 25, 2015
    On Windows 10 build 10041, SDK 4.4, I initially had this error message:

    There is a problem with your Rift configuration.
    Interfering software is preventing the Rift from activating. Loaded UMD is reported as 'aticfx64.dll'.

    Updating to the latest AMD Beta driver, amd-catalyst-15.3beta-64bit-win8.1-mar20.exe, resolved the issue.
    New Participant
    March 30, 2015
    "wadeb" wrote:
    On Windows 10 build 10041, SDK 4.4, I initially had this error message:

    There is a problem with your Rift configuration.
    Interfering software is preventing the Rift from activating. Loaded UMD is reported as 'aticfx64.dll'.

    Updating to the latest AMD Beta driver, amd-catalyst-15.3beta-64bit-win8.1-mar20.exe, resolved the issue.


    I had the exact same problem. Thanks for the fix!