Can't see my local printer on the connected Remote Desktop (Windows app on macOS)

I cannot see my printer on the remote desktop I connect to. The Printer redirection setting is enabled in the Windows app, and it worked with the same settings under an older iMac running Monterey. After upgrading to a MacBook Air M1, I can no longer see my printer when connecting to a Windows Server 2012 R2 system.

Environment:

• Local Device: MacBook Air M1 running macOS 15.3.1
• Remote Desktop Client: Windows App (11.1.2) from the Mac App Store
• Printer: EPSON L6290 with latest drivers and firmware
• Remote Server: Windows Server 2012 R2

Troubleshooting Performed:

• Confirmed printer redirection is enabled in the Windows app settings
• Verified that the printer works correctly with macOS
• Tested connecting to a Windows 11 laptop instead of the server, and printer redirection worked properly
• Previously used the same Windows Server 2012 R2 with an older iMac running Monterey and printer redirection worked correctly
• Downloaded an older version of the Windows App (older than v10.9.4) and was able to see the printer on Remote Desktop, but could not print (possibly due to Apple removed PSNormalizer in the Sonoma update)

After some research on this issue, I discovered a Microsoft Learn post stating that printing from Remote Desktop broke after updating to macOS Sonoma (link). According to the thread, the problem was supposedly fixed in Windows App v10.9.4 (2160).

Based on my testing, this fix appears to be partial:

• Printer redirection works perfectly when connecting from my MacBook Air M1 to my old laptop running Windows 11 with remote desktop enabled but not working when connecting to a Windows Server 2012 R2

Could this be a specific issue with Windows Server 2012 R2 that wasn't fully addressed in the v10.9.4 fix? 

Are there any workarounds available for this specific scenario with Windows Server 2012 R2, will there be fix/patch for the WIndows app? This is very important for me because of my job, and I hope this issue can be fixed with an app update, as our company probably won't update the server because of this.