So, I'm running Win10 if that matters, but I cannot get the controls to do....anything after the game runs through the intro movies. It gets to the start screen where you can select to start a new game and such, and nothing works. My mouse doesn't move, my keyboard won't activate any menu choices, if I have a gamepad connected, nothing works there, either.

I tried adding "UseMouseDamp=True" to the User config file, but that didn't do anything.

What gives?

I assume that we are talking about the vanilla-version (and you didn't ruin your installation by using cheats, mods, console commands etc.).

Try out:

* Hold SHIFT. Can you move the cursor now?

* Try to repair your installation by using GALAXY (Choose the game -> nameless symbol on the top right side -> manage installation -> Verify/repair).

* Try to start the game without GOG:
- Shut down GOG completely.
- Use the explorer to seek for witcher2.exe. Try to start the game using the .exe.

Well, I tried the repair approach. I then tried uninstalling and reinstalling. Neither of those things fixed it.

I'll give the SHIFT and non-GOG launch approaches a try.

--edit--

Ok, I tried holding SHIFT and moving the mouse. No luck.

I tried launching the game from the launcher, rather than GOG. No luck.

I tried launching the game from the witcher2.exe with Galaxy shut down. No luck.

I tried launching the game from the witcher2.exe with Galaxy shut down, AND the application set to Win7 for compatibility mode. No luck.


I don't know if this makes a difference, but I have a bluetooth keyboard and mouse. But, the mouse actually works to click through the opening cinematics. In other words, I can skip them by clicking the mouse button, but as soon as the menu loads and I try to move the mouse, nothing happens. Nor do the keys work.

Try doing a cold reboot of your computer.

Yup. That did it. Weird...but it works.

I got the same problem, but the cold reboot didn't do it for me.

If your bios has a "fastboot" option, try going in and disabling it, and then reboot.
If it solves the problem you can then go back and re-enable fastboot.