Command prompt settings do not save

bro67 said:

"When you open Command Prompt and position it on your preferred location on the screen, the setting is not retained. Also, when you resize the Command Prompt window and close it, the setting is not saved." After you make the registry changes and reboot, some times you may not get the same Defaults if done in the registry entry for Current User. You have to do it at Machine level.

"Difference between “Properties” and “Defaults” options

Right-clicking on the Command Prompt window title offers access to the Properties dialog box. (If Command Prompt is running in full-screen mode, press Alt+Enter to switch to window display.) Changes you make here affect the current session, and all future sessions launched only from that shortcut. The changes made are saved inside that particular shortcut (.lnk) file, instead of the registry.


Right-clicking on the Command Prompt window title and choosing Defaults from the Control menu lets you make changes that will not affect the current session but instead will affect all future sessions (except for those launched from a shortcut whose properties have been customized). These changes also affect future sessions in character-mode, MS-DOS-based applications that do not have a Program Information File (PIF) and do not store their own settings. This setting is saved in the registry." See Where are cmd.exe's settings in registry in Windows 10? - Super User

I realize that in my screenshot it says that I'm looking at the "Console Windows Properties", but I'm not, that is the title of the window that opens when I click on "Defaults". It's a bit misleading I know.
Here's a video gif on imgur of the problem:

Imgur: The magic of the Internet

I tried the registry instructions from the superuser link and then rebooted, but the problem persists.

I checked out the new Terminal preview from Microsoft, it looks pretty nice, the app starts in a proper size but the text in the terminal doesn't fit the whole screen, so the issue persists.



Not sure if this is important but I noticed that when I open cmd, the proper settings appear for a split second, then it reverts back to the issue.

bro67 said:

MS did change that the registry hive is no longer backed up and any software that syncs your computer or it runs into some odd issue and rolls back, along with being on a domain, this profile can revert back.

I don't get you. What do you mean by Registry hive and profile reverting?

bro67 said:

The Registry is called a Registry Hive. Your Profile can cause your settings to not stick or revert back if some third party software is running or your computer is on a domain.

Well, my Pc isn't on any domain, maybe a third party software or virus?
I'll do a full scan and update you.

- - - Updated - - -

bro67 said:

The Registry is called a Registry Hive. Your Profile can cause your settings to not stick or revert back if some third party software is running or your computer is on a domain.

I did a full-scan, found some Malware, adware and Rootkits surprisingly.
There's no way to tell if it had anything to do with cmd specifically, but does that mean I can't fix cmd itself?
Do I have to do a fresh windows install? I guess I could've just reformatted and reinstalled windows but I guess that wouldn't be finding the real solution. It's such a pain too, to reinstall everything.

Why MS have decided to screw with the way executables are run baffles me, so much for standards. Just give us a damn .exe and in ONE location to work with!

@OP - have you checked the properties of the Command Prompt shortcuts in:

Code:

%LOCALAPPDATA%\Microsoft\Windows\WinX\Group3\

If not, change them both to what you want and then run cmd.exe from the Run dialogue, NOT from Explorer or an existing shortcut (i.e. <WIN>+<R> and type 'cmd').

Report back.

Out of frustration, I ended up deleting everything and resetting my PC (Sorry). Thankfully the problem didn't persist this time around, although I still don't know why it happened or if I could've solved it.

Thanks a lot folks!
Not sure if I should mark this as resolved or what.