When I move the cursor over the portraid mode monitor, it shows up in a different spot than the edge, and it moves up and down when I go left-right as if it's in landscape mode. The only solution is to physically disconnect the monitor and reconnect it.

This also happens when I manually activate it and set it to portraid mode in windows settings, so it does seem to be a windows issue.

Edit : I contacted windows support and they did the following :
"I have restarted the essential services, removed and reinstalled the drivers, checked for and installed optional driver updates, and reviewed the Advanced System Settings to ensure they are configured correctly in an effort to resolve the issue."

Now when I enable the display via windows settings, the issue does not occur. When I use DF to switch display profiles, it does still occur.

As per the same windows support staff member : "The third-party application may be applying an outdated or incompatible display profile, especially after recent Windows or graphics driver changes."

For now, I can activate the offending display in windows settings and then switch display profile in DF. Which is an improvement, but I'm hoping it can be fully resolved.

If you're asking if I configured the monitor orientation for the display profile in windows settings or in displayfusion, I honestly don't remember. At least not for the one I am switching to (which is the original/default one), I do set the other display profiles in displayfusion though.

I just tried that, and the issue also occurred.

Hi,

I'm having the same issue.

I compared three BFCustomerTest exports: before applying the configuration with DisplayFusion, afterwards, and after a Windows graphics reset.

All 11 configuration sections are identical, including monitor positions, resolutions, refresh rates, scaling, rotation, display paths and mode data. Only the diagnostic tool’s startup logs differ.

The setup is an RTX 4080 with a Samsung G93SC at 5120×1440/240 Hz and a Dell P2422H in portrait at 1080×1920/60 Hz, both at 100% scaling. The Dell’s active path consistently reports ROTATE90, including in the faulty state.

The exports therefore show no configuration change explaining the cursor issue. An internal cursor/rotation state problem remains possible, but these files alone cannot establish the cause.

I have attached these three files for your analysis.

Best regards,
Thomas