New installation of Windows causes strange sens issue

[XeroJager]

Hi guys,

I'm having a strange issue with a fresh install of Windows 10 that I applied to my PC last weekend (May 27th) where my current setup is yielding a shorter Inch/360 than it was previously.

Here's what my settings were on my previous installation of Windows 10:

• Core i7 4790K
• GTX 1070
• Razer Deathadder Elite (Previously used Deathadder Chroma)
• Used settings akin to 10.22-10.25inch/360.
• Games mostly played:
• Quake 1-3 (Including CPM): Sensitivity 2.0
• Reflex: Sensitivity 7.65
• NO ingame accel anywhere.
• Windows "enhanced pointer" mouse accel off
• WPS 6/11
• Windows scaling set at 100% @ 1920x1080

---------------------

The new installation of windows uses the exact same setup, except now i'm getting closer to 9.5inch/360 than my usual measurement. All previous windows installation calculations were done using the sensitivity calculator on this website, and were 1:1 up until the new installation of windows.

The actions i've done so far:

• Run my Deathadder elite clean, no software on/installed.
• Run my Deathadder elite with Razer Synapse software on
• Used a different mouse entirely: Cheap logitech M100 I got from work.
• Cleaned both sensors for good measure.
• With both mice, ran the Enotus mouse test, found that my Deathadder, which was set to 800 DPI, was running closer to 900+, and the M100, listed as 1000DPI, ran closer to 1200+.
• Ran the MarkC Fix for 100% scale, which is what my PC was set to. No effect. Reverted action afterwards.
• Installed/Uninstalled Razer Synapse multiple times. No effect.
• Changed mouse polling rate from 1000hz, 500hz, and 125hz. No effect.
• Uninstalled Windows Game Bar through Windows Powershell. Made sure it was off in registry. No effect.
• Double checked to make sure Windows enhanced pointer was off, it was.
• Double checked to see if Windows was set to 6/11 for pointer speed. It was.
• Installed newest USB Drivers for my motherboard. 
• Physically measured mouse distance in multiple games a 360 turnaround from a reference point, got consistent measurements of 9.5in/360
• Used both mice on another PC to confirm it wasn't the mice hardware. Can confirm mice are fine.

-------------------------

 

I'm pretty stumped, and figured this would be the correct place to ask. Open to any and all suggestions at this point.

Thank you,

-J
 

Edited June 3, 2017 by XeroJager

[DPI Wizard]

Sounds like you have gone through most points of failure, strange issue. Was the old installation of Windows also 10?

12 hours ago, XeroJager said:

• With both mice, ran the Enotus mouse test, found that my Deathadder, which was set to 800 DPI, was running closer to 900+, and the M100, listed as 1000DPI, ran closer to 1200+.

PS, you can measure DPI here too

[XeroJager]

54 minutes ago, DPI Wizard said:

Sounds like you have gone through most points of failure, strange issue. Was the old installation of Windows also 10?

PS, you can measure DPI here too

Can confirm that my previous installation of Windows was also Windows 10.

Can also confirm that by using the DPI Analyzer on this site, i'm coming up with the same results as before.

-J

[Drimzi]

Edited January 28, 2018 by Drimzi

[XeroJager]

11 minutes ago, Drimzi said:

Have you tried redownloading the latest Windows 10 ISO or the older versions? Something could be wrong with the ISO you used.

All official Windows ISOs can be found here, with downloads directly from the Microsoft servers: https://tb.rg-adguard.net/index.php

I used the Windows Media Creation Tool to make a bootable drive to install windows. I would assume it's the latest ISO they have. Not 100% sure though. Other than the mouse issue this installation of Win10 looks pretty much standard. It's been updated to the latest build as well. Any way to check which version it was installed with?

-J

[Drimzi]

Edited January 28, 2018 by Drimzi

[XeroJager]

4 hours ago, Drimzi said:

You can press "WIN+R" to open Run, then type "winver" to view the version, but Windows Update would update to the latest version anyhow.

You can try the older Windows 10 versions to see if the problem is fixed. That would rule out the OS.

Can confirm i'm running newest version.

I'd like to see if I can find any other discrepancies/solutions before I go through with another reformat/reinstall. I know I can install another Win10 ISO without clearing my files, but I don't want to take the risk of having the same issue arise on the new install.

-J

[Drimzi]

Edited January 28, 2018 by Drimzi

[XeroJager]

21 hours ago, Drimzi said:

The fastest way to fix is to reinstall. You said you tested the mice on another computer and the mice were fine. So it's either software or hardware related. Reinstall, then you know if it is fixed or not. If it is not, then something might be wrong with your motherboard, like the usb hub. If it is fixed, then it's some tweak or software causing your issue. Repeat your tweaks, install your software and find out when it breaks.

Following up on this,

 

I've reinstalled Windows 10 using the 1607 [July 2016] Build ISO on the site you suggested. It went ahead and ran all of it's updates so it's using the current version of Windows 10.

I've gone through and made all my settings the same in my games/windows.
WPS 6/11
1920x1080 at 100% scale

I went through and tested the mouse with these stipulations:
USB Drivers not updated - Same problem as before.
USB Drivers updated - Same problem as before.
Used both Deathadder and Logitech M100 - Same problem as before, showing closer to 900 and 1200 DPI respectively, rather than 800 and 1000.
Used both mice on different USB ports, USB 2 and 3 alike - Same problem as before.

The only thing I haven't done is reinstall Razer Synapse or apply the MarkC fix, of which had no effect on the situation anyway.

-J

 

[arfarf]

I was fighting with mouse sensitivity issues for over 7 months before thanks to the development of DPI scaling in Windows 10.

It actually reached the point where I just somehow landed between me being insane and something must be wrong and accepted it. But when it fixed itself suddenly from a fix that didnt fix it several months earlier I knew I wasnt insane since suddenly I got reminded how it is supposed to be and recognized it instantly. Ironicly the time that had passed required me to get used to the new-old correct setting again. I still dont know exactly today what caused it, but I do know its related to Windows 10 and the way it scales things. But I could raise ingame settings with around 20% again and still feel it wasnt enough.

It seem to be more common with a high dpi monitor with 1440p or higher resolutions. But the issue can be anything from your previous Windows doing some dumb assumption from your previous monitor driver (even if just a basic one provided by windows) and doesnt with your "new" to that they simply have "fixed" something that comes in one of the updates after your fresh install anyway. If I havent understood it completely wrong Microsoft provides updates to each version so installing 1607 with any update can still give "fixes" that didnt appear until later, because as long as you can update any version it is considered as an old version but supported just as Windows XP, 7 and so on was/is. Its just shorter time its supported. (1607 ended its support 10th april 2018 or something).

No matter what you do with your scaling settings it seem (based on all the various issue threads out there) that your settings can all look fine, such as 100% scaling and so on while things that are just impossible for us consumers to find can be what causes it and many dont encounter this problem and its hard to find relevant info about it since 99% of what you find will be answered by people that thinks its just a "normal" problem that could get fixed with "have you unchecked enhanced pointer precision?" or questions like "is your windows setting on 6/11" when the problem is way more deeper than that and can make you question your sanity since its so hard to pin point or find spot on threads with similar issues.

Another thing that adds to the problem is all the different overlays that exist. Override DPI scaling for .exe's a couple months ago could be completely irrelevant as soon as any overlay (NVIDIA, Discord, Steam for example) was active. Or sometimes when you had minimized once to desktop and no matter what you did after it was just a mess. You had to figure out the .exe for those too and override dpi scaling. But even if you did that, the mouse behaved different in the NVIDIA overlay but of course sometimes it didnt. Just a big mess.

I dont have any solution to your problem, but I hope you got some clues or new ideas on how to find your issue. You should try do your test in the restore environment (shift+select restart) since any scaling or OS related things should be deactivated there but double check that on google since Im not 100% if you enter the restore environment completely just with that.

And about the Xbox game bar, game mode etc. Apparently its not as easy as just uninstall through powershell and the single reg fix anymore.

Try save this as .bat and run it (at your own risk) to completely remove Xbox, DVR and turn off game mode.

 

@echo off
goto check_Permissions
:check_Permissions
    echo Administrative permissions required. Detecting permissions...
    net session >nul 2>&1
    if %errorLevel% == 0 (
        echo Success: Administrative permissions confirmed.
reg add "HKLM\System\CurrentControlSet\Services\xbgm" /v "Start" /t REG_DWORD /d "4" /f
sc config XblAuthManager start= disabled
sc config XblGameSave start= disabled
sc config XboxGipSvc start= disabled
sc config XboxNetApiSvc start= disabled
schtasks /Change /TN "Microsoft\XblGameSave\XblGameSaveTask" /Disable
takeown /f "%WinDir%\System32\GameBarPresenceWriter.exe" /a
icacls "%WinDir%\System32\GameBarPresenceWriter.exe" /grant:r Administrators:F /c
taskkill /im GameBarPresenceWriter.exe /f
move "C:\Windows\System32\GameBarPresenceWriter.exe" "C:\Windows\System32\GameBarPresenceWriter.OLD"
schtasks /Change /TN "Microsoft\XblGameSave\XblGameSaveTask" /Disable
takeown /f "%WinDir%\System32\bcastdvr.exe" /a
icacls "%WinDir%\System32\bcastdvr.exe" /grant:r Administrators:F /c
taskkill /im bcastdvr.exe /f
move C:\Windows\System32\bcastdvr.exe C:\Windows\System32\bcastdvr.OLD
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\GameDVR" /v "AppCaptureEnabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\GameBar" /v "UseNexusForGameBarEnabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\GameDVR" /v "AudioCaptureEnabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\GameDVR" /v "CursorCaptureEnabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\GameBar" /v "ShowStartupPanel" /t REG_DWORD /d "0" /f
reg add "HKCU\System\GameConfigStore" /v "GameDVR_Enabled" /t REG_DWORD /d "0" /f
reg add "HKLM\Software\Policies\Microsoft\Windows\GameDVR" /v "AllowgameDVR" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\GameBar" /v "AllowAutoGameMode" /t REG_DWORD /d "1" /f
) else (
        echo Failure: Current permissions inadequate.
    )
    pause >nul

 

 

Edited June 3, 2018 by arfarf
Some (probably not all) spelling derps