[BUG] WinX Command Prompt shortcuts don't retain opacity preference

John Doe 21 Reputation points
2021-01-02T12:09:01.187+00:00

Setting the opacity preference of a Command Prompt (regular or "Admin") launched through the Win+X shortcut (via Properties > Colors page) is not saved/retained at the relaunch of the program
If the preference is changed in cmd.exe launched through the Run (Win+R) dialog then it is preserved at the next launch.
I've noticed this behavior in both Windows Server 2019 and in Windows 10 1809 LTSC (latest CU applied to both the OSes) and to both RTM versions (tested as VMs in Hyper-V)

Tags: Windows-Server-2019 Windows-10-1809 cmd.exe conhost.exe opacity

52838-winx-cmd-opacity-bug0.png52839-winx-cmd-opacity-bug1.png52739-winx-cmd-opacity-bug2.png52872-winx-cmd-opacity-bug3.png

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,790 questions
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2021-01-02T13:35:37.713+00:00

    You can report this as feedback over here on uservoice.
    https://windowsserver.uservoice.com/forums/295047-general-feedback

    or you can also start a case here with product support. A card is required to secure the support contract but confirmed bugs are never charged.
    https://support.serviceshub.microsoft.com/supportforbusiness

    --please don't forget to Accept as answer if the reply is helpful--

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
  1. Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,756 Reputation points Microsoft Vendor
    2021-01-04T02:50:28.18+00:00

    Hi,

    It is not a bug.

    Setting the opacity preference of a Command Prompt (regular or "Admin") launched through the Win+X shortcut (via Properties > Colors page) is not saved/retained at the relaunch of the program

    Actually, the settings are saved at the relaunch. You should relaunch the program still by Win+X shorcut. Then you will see the opacity preference is retained.

    And if you open cmd.exe launched through the Run, the settings are not the same as Command started by Win+X.

    This is because they are different programs —— Command.com (win+X) and cmd.exe (run). So, the settings between them are different.

    For your reference:
    https://superuser.com/questions/451816/what-is-the-difference-between-cmd-and-command-prompt-in-windows
    https://www.itprotoday.com/devops-and-software-development/what-difference-between-cmdexe-and-commandcom
    https://stackoverflow.com/questions/34068830/whats-the-difference-between-command-prompt-and-cmd

    Thanks,

    Eleven

    If the answer is helpful, please click "Accept Answer" and up-vote it.

    0 comments No comments

  2. John Doe 21 Reputation points
    2021-01-04T12:00:34.03+00:00

    @Eleven Yu (Shanghai Wicresoft Co,.Ltd.) Thank you for your reply

    Actually, the settings are saved at the relaunch. You should relaunch the program still by Win+X shorcut. Then you will see the opacity preference is retained.

    I did, and in Windows Server 2019 (and also in Windows 10 1809 LTSC) it didn't save it

    In Windows 10 1903 and upwards all is good, I set the opacity and the next relaunch (always with Win+X) it retain it

    Have you actually tried to replicate it?

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.