Raphire
Fullscreen Apps are flickerung and the desktop is shing through when i klick at the boderless screen
Hi,
I did the fully Debload Package and after it my Boderless Apps are flickerung and the desktop is shing through when i klick at the Boderless app. I need to switch to Fullscreen and than to Boderless. Than the Problem is solved. But only until i restart the Game.
Does sombody know waht to do?
Heya,
I'm unsure how the script could cause this issue. A quick google search seems to suggest this may be graphics-driver related. Disabling freesync or G-sync on your monitor, or in the graphics driver, seems to have helped in those cases.
See: https://www.reddit.com/r/techsupport/comments/svf531/screen_flickers_while_gaming_in_borderless_window/ and: https://www.reddit.com/r/radeon/comments/lq9hsc/flicker_when_on_windowed_borderless_or_fullscreen/
I had the same problem, every time I entered the full screen game, the screen would keep flashing.
Heya,
I'm unsure how the script could cause this issue. A quick google search seems to suggest this may be graphics-driver related. Disabling freesync or G-sync on your monitor, or in the graphics driver, seems to have helped in those cases.
See: https://www.reddit.com/r/techsupport/comments/svf531/screen_flickers_while_gaming_in_borderless_window/ and: https://www.reddit.com/r/radeon/comments/lq9hsc/flicker_when_on_windowed_borderless_or_fullscreen/
Hi, no there is no Problem with G-Sync. The Graphic Drivers are also reinstalled.
Heya, I'm unsure how the script could cause this issue. A quick google search seems to suggest this may be graphics-driver related. Disabling freesync or G-sync on your monitor, or in the graphics driver, seems to have helped in those cases. See: https://www.reddit.com/r/techsupport/comments/svf531/screen_flickers_while_gaming_in_borderless_window/ and: https://www.reddit.com/r/radeon/comments/lq9hsc/flicker_when_on_windowed_borderless_or_fullscreen/
Hi, no there is no Problem with G-Sync. The Graphic Drivers are also reinstalled.
That's unfortunate. Is HDR enabled in Windows?
I can also confirm the described effect. It started exactly after debloating & reset.
@josuakuehnel Do you have any updates on this?
No update to this case. I guess i have to reinstall Windows, to solve it. But i have to say, i didnt put any more affort in it.
@josuakuehnel @mseroczynski
Do you happen to remember what settings you used when executing the script? Was it just the default?
Do you happen to remember what settings you used when executing the script? Was it just the default?
It was default/ full script.
In my case it have 'fixed itself' (probably after NVIDIA clean drivers reinstall).
In my case it have 'fixed itself' (probably after NVIDIA clean drivers reinstall).
Interesting. Nvidia's drivers have been a bit wonky the past few months, and a recent driver seems to have fixed a wide range of issues. I'm unsure if that contributed here. I'll keep monitoring this to see if the problem persists with others.
Hi, I just want to leave a comment here to let you know that I am also experiencing the issue. Have tried clean reinstall of Windows and this happens exactly after I am using the debloat script. I am running it on default. My GPU is RX 6800 XT.
Sometimes it happens when i run a game on windowed mode, and when i try to drag my game's window it will crash and BSOD.
Hi, I just want to leave a comment here to let you know that I am also experiencing the issue. Have tried clean reinstall of Windows and this happens exactly after I am using the debloat script. I am running it on default. My GPU is RX 6800 XT.
Sometimes it happens when i run a game on windowed mode, and when i try to drag my game's window it will crash and BSOD.
Hmm, so It's not just limited to nvidia cards. Do you happen to remember the BSOD error code?
I had these exact same issues and with the help of Claude AI, we eventually tracked it down to this debloater script!
Interestingly I had the issue on both Windows 10 and Windows 11 after running this same debloater on each.
I can't say 100% which command caused it, but Claude picked the most suspicious tweaks out and reversed them and when I ran this reversal script in powershell as admin, it instantly fixed my problem! (after a reboot)
Claude thinks the desktop timings or mouse settings were the most likely culprits.
I hope this helps someone!
Reset desktop timing settings
Set-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name "MenuShowDelay" -Type String -Value 400 Set-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name "WaitToKillAppTimeout" -Type String -Value 20000 Set-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name "HungAppTimeout" -Type String -Value 5000 Set-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name "LowLevelHooksTimeout" -Type DWord -Value 5000 Set-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name "AutoEndTasks" -Type DWord -Value 0
Reset mouse settings
Set-ItemProperty -Path "HKCU:\Control Panel\Mouse" -Name "MouseHoverTime" -Type String -Value 400
Reset window animation settings
Set-ItemProperty -Path "HKCU:\Control Panel\Desktop\WindowMetrics" -Name "MinAnimate" -Type String -Value 1 Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" -Name "TaskbarAnimations" -Type DWord -Value 1
Reset keyboard delay
Set-ItemProperty -Path "HKCU:\Control Panel\Keyboard" -Name "KeyboardDelay" -Type DWord -Value 1
Reset listview settings
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" -Name "ListviewAlphaSelect" -Type DWord -Value 1 Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" -Name "ListviewShadow" -Type DWord -Value 1
Write-Output "Reset all window/input/timing settings. Reboot and test."
ListviewShadow
I had these exact same issues and with the help of Claude AI, we eventually tracked it down to this debloater script!
Interestingly I had the issue on both Windows 10 and Windows 11 after running this same debloater on each.
I can't say 100% which command caused it, but Claude picked the most suspicious tweaks out and reversed them and when I ran this reversal script in powershell as admin, it instantly fixed my problem! (after a reboot)
Claude thinks the desktop timings or mouse settings were the most likely culprits.
I hope this helps someone!
Reset desktop timing settings
Set-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name "MenuShowDelay" -Type String -Value 400 Set-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name "WaitToKillAppTimeout" -Type String -Value 20000 Set-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name "HungAppTimeout" -Type String -Value 5000 Set-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name "LowLevelHooksTimeout" -Type DWord -Value 5000 Set-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name "AutoEndTasks" -Type DWord -Value 0
Reset mouse settings
Set-ItemProperty -Path "HKCU:\Control Panel\Mouse" -Name "MouseHoverTime" -Type String -Value 400
Reset window animation settings
Set-ItemProperty -Path "HKCU:\Control Panel\Desktop\WindowMetrics" -Name "MinAnimate" -Type String -Value 1 Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" -Name "TaskbarAnimations" -Type DWord -Value 1
Reset keyboard delay
Set-ItemProperty -Path "HKCU:\Control Panel\Keyboard" -Name "KeyboardDelay" -Type DWord -Value 1
Reset listview settings
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" -Name "ListviewAlphaSelect" -Type DWord -Value 1 Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" -Name "ListviewShadow" -Type DWord -Value 1
Write-Output "Reset all window/input/timing settings. Reboot and test."
Heya @Dragynrain,
Glad you managed to fix it, and I appreciate you sharing this with others here. From what I can find however, none of the registry keys that are mentioned in your reply are changed by Win11Debloat. Did you use any other tools or scripts that may have changed these keys?
Heya @Dragynrain,
Glad you managed to fix it, and I appreciate you sharing this with others here. From what I can find however, none of the registry keys that are mentioned in your reply are changed by Win11Debloat. Did you use any other tools or scripts that may have changed these keys?
I feel super silly! It was a different debloater. And I wonder if other people have done the same thing and used more than one potentially. When I was searching for issues after fixing it, this was the first and seemingly obvious choice for which one I ran. On further digging though, this is the debloater I actually used:
https://freetimetech.com/windows-10-clean-up-debloat-tool-by-ftt/
So if someone else does run into that - it may be caused by a different debloater.
I'll have to dig into some of the github sources they used to make their debloater to see if I can find these keys mentioned upstream of this project.
Heya @Dragynrain, Glad you managed to fix it, and I appreciate you sharing this with others here. From what I can find however, none of the registry keys that are mentioned in your reply are changed by Win11Debloat. Did you use any other tools or scripts that may have changed these keys?
I feel super silly! It was a different debloater. And I wonder if other people have done the same thing and used more than one potentially. When I was searching for issues after fixing it, this was the first and seemingly obvious choice for which one I ran. On further digging though, this is the debloater I actually used:
https://freetimetech.com/windows-10-clean-up-debloat-tool-by-ftt/
So if someone else does run into that - it may be caused by a different debloater.
I'll have to dig into some of the github sources they used to make their debloater to see if I can find these keys mentioned upstream of this project.
No worries! Thanks for the detailed response. I hope that the fix you mentioned helps other people.
Heya @Dragynrain, Glad you managed to fix it, and I appreciate you sharing this with others here. From what I can find however, none of the registry keys that are mentioned in your reply are changed by Win11Debloat. Did you use any other tools or scripts that may have changed these keys?
I feel super silly! It was a different debloater. And I wonder if other people have done the same thing and used more than one potentially. When I was searching for issues after fixing it, this was the first and seemingly obvious choice for which one I ran. On further digging though, this is the debloater I actually used: https://freetimetech.com/windows-10-clean-up-debloat-tool-by-ftt/ So if someone else does run into that - it may be caused by a different debloater. I'll have to dig into some of the github sources they used to make their debloater to see if I can find these keys mentioned upstream of this project.
No worries! Thanks for the detailed response. I hope that the fix you mentioned helps other people.
So, I encountered the same problem here and did the same thing as the person above, it didn't fix the problem at all. I've never used another debloater other than this one. Really hoping for a potential fix on this.
Heya @Dragynrain, Glad you managed to fix it, and I appreciate you sharing this with others here. From what I can find however, none of the registry keys that are mentioned in your reply are changed by Win11Debloat. Did you use any other tools or scripts that may have changed these keys?
I feel super silly! It was a different debloater. And I wonder if other people have done the same thing and used more than one potentially. When I was searching for issues after fixing it, this was the first and seemingly obvious choice for which one I ran. On further digging though, this is the debloater I actually used: https://freetimetech.com/windows-10-clean-up-debloat-tool-by-ftt/ So if someone else does run into that - it may be caused by a different debloater. I'll have to dig into some of the github sources they used to make their debloater to see if I can find these keys mentioned upstream of this project.
No worries! Thanks for the detailed response. I hope that the fix you mentioned helps other people.
So, I encountered the same problem here and did the same thing as the person above, it didn't fix the problem at all. I've never used another debloater other than this one. Really hoping for a potential fix on this.
Heya, what settings did you select when you ran the script?