`MouseHoverTime` registry entry gets `incorrectly` converted to DWORD.

RaulGonzalezPortillo commented 1 year ago

Describe the Bug

In line 109 from optimize-performance, the script changes the DWord entry "MouseHoverTime" to 10, from 400.

Write-Status -Types "+", $TweakType -Status "Reducing mouse hover time events to 10ms..."
Set-ItemProperty -Path "HKCU:\Control Panel\Mouse" -Name "MouseHoverTime" -Type DWord -Value 10 # Default: 400

But MouseHoverTime is originally a String Value. By changing it's type, Windows ignores this value and defaults to 0, which, for example, causes the Widgets and Task View hover events to trigger instantly if you happen to go over them while trying to reach the start button with your mouse.

How can this issue be reproduced?

Execute the optimize-performance script.

Expected behavior?

No response

Operating System

Windows 11

Operating System Version

22H2 (Build 22621.1194)

Screenshots

No response

Logs

No response

Additional Info

No response

LeDragoX commented 1 year ago

Thanks, i didn't realized the reason which this tweak wasn't working properly, i'll test and change the type from Dword to String 😉

KevinJamesSmirking commented 11 months ago

Dude I think you kinda fucked up, the MouseHoverTime is set to "1000". Or are you doing some voodoo shit with the String?

edit: might be my sleepy ass tho so no worries

cakiya commented 8 months ago

Dude I think you kinda fucked up, the MouseHoverTime is set to "1000". Or are you doing some voodoo shit with the String?

edit: might be my sleepy ass tho so no worries

no you are right; after running script i tried to hover over some taskbar icons and it took longer than usual to appear (i use ghelper and noticed that it was coming up alot slower. i hover over it often to see how much battery i'm using).

this can be fixed by changing it to default value of 400, or the intended 10, not 1000.

LeDragoX / Win-Debloat-Tools