Hi Karen,
My name is Jason and I am an independent advisor and windows user like yourself.
The erratic behavior of web pages going "back" when using a wireless mouse after a Windows 10 to Windows 11 upgrade points strongly to an issue with misinterpreted driver input or a conflict caused by an old peripheral driver that didn't clean up properly during the upgrade.
The fact that using the NetFX (presumably .NET Framework) repair tool provides temporary relief is a very unusual but crucial clue, suggesting the problem might be linked to a core component that interprets input events, which the mouse driver relies on. Here is a focused plan to address this issue, moving beyond simple reinstallation and focusing on driver conflicts and input interpretation: Check for Misinterpreted Mouse Buttons (Most Likely Cause) Many wireless mice have side buttons (often used for forward/back in browsers). Windows 11 may be incorrectly registering a slight scroll or tap as a side-button click.
Remove the Mouse Driver: Press Windows Key + X and choose Device Manager. Expand the Mice and other pointing devices section. Right-click your mouse entry (it might say "HID-compliant mouse") and select Uninstall device. Restart your PC. Windows will reinstall a generic driver, which can clear up corrupted settings.
Test in Safe Mode: Booting into Safe Mode loads only essential drivers. If the problem disappears in Safe Mode, the issue is definitely a non-essential driver conflict. Use Manufacturer Software (If Available): If your mouse (Logitech, Razer, etc.) has its own software, install it. This software often allows you to disable or remap the side buttons, which will stop the unintended "back" action completely. Deep Clean of Peripheral Drivers (The Upgrade Conflict) A dirty upgrade can leave behind residual driver components that conflict with Windows 11. Run the System File Checker (SFC): This ensures no core Windows system files are corrupted (which might be why the .NET repair tool helps temporarily). Open Command Prompt as Administrator. Type sfc /scannow and press Enter. Let it complete.
Check for Residual Drivers (DriverStore Explorer): This requires a third-party tool but is excellent for cleaning up old, conflicting drivers left over from the upgrade. This is often necessary when a clean OS reinstallation doesn't fix a hardware issue.
Adjust Touchpad/Scrolling Sensitivity
Even if you are using the mouse, some input interpretation conflicts can be related to touchpad drivers running in the background. Go to Settings \rightarrow Bluetooth & devices \rightarrow Mouse. Scroll down to the Related settings and click Additional mouse settings. Navigate through the tabs (often labeled "Hardware" or "Device Settings") and look for a setting related to scrolling sensitivity or accidental input prevention. Try slightly reducing the scrolling speed.
Why the NetFX Repair Tool Provides Relief The temporary fix you get from the .NET Framework repair tool is a significant clue. It suggests that the application responsible for handling the mouse input (perhaps a browser component or a specific Windows service) is dependent on the .NET Framework for part of its functionality. When the repair tool runs, it essentially refreshes those dependencies, providing a brief window of stability before the underlying driver conflict resurfaces. This reinforces the need for a driver deep-clean (Step 2).