2026.3 is a bit of a joke

Answered

Terminal stopped working on windows, gitbash terminal, command prompt, powershell all dead. All dead except the WSL terminal.
So I decided to switch my maven project to run in WSL. Worked fine for about ten minutes, then despite the fact that the project works absolutely fine in maven in the command line, IntelliJ decided to ignore this and proceeded to refuse to compile or run within IntelliJ.

Reverting back to 2026.2.4 fixes the terminal issue, so back to 2026.2.4 and no WSL.

0
1 comment

Hi Alfonso, 

Thank you for reaching out, though I'm sorry to hear you're experiencing this issue. 

The terminal problem may match a known IntelliJ IDEA 2026.3 issue related to the GitHub Copilot modernization plugin: IJPL-260821.

Could you please check Settings | Plugins | Installed for GitHub Copilot modernization? If it is installed, please disable only that plugin, restart IntelliJ IDEA, and check whether PowerShell, Command Prompt, and Git Bash work again. The regular GitHub Copilot plugin can remain enabled.

Regarding Maven and WSL, could you please clarify the following?

  • Is the project stored inside WSL, for example under \wsl.localhost\..., or on the Windows file system, for example under C:\...?
  • You mentioned that IntelliJ refuses to compile or run. Does the Maven compile goal fail in the Maven tool window, or does compilation succeed and only the application Run configuration fail?
  • What is the exact error message shown in the Maven or Run tool window?
  • You mentioned that Maven works from the command line. Which command succeeds, and does the same command fail when started from IntelliJ IDEA's Maven tool window?
  • Which Maven distribution and Maven JVM are selected in Settings | Build, Execution, Deployment | Build Tools | Maven?
  • Does the WSL terminal tab itself reopen as PowerShell after restarting IntelliJ IDEA, or does it remain a WSL terminal and only the Maven operation fail?
  • After disabling GitHub Copilot modernization, does the Maven/WSL problem still occur?

These details will help us determine whether the Maven behavior matches an existing WSL path/import issue or is separate from the terminal problem. Thank you!

 

0

Please sign in to leave a comment.