Always have the console displayed

[texas2607]

Hi, In the configuration file I have : : ShowConsoleWindowOnStartup=0 But when I start Windows, I always have the console displayed

Any idea ? Thk

[HerMajestyDrMona]

Hi. This is strange. Even when there is no configuration file it should not display the console window on startup (default configuration since version 1.8 I think). Could you paste the full content of your config file?

[texas2607]

//Should the program run automatically on system startup? //1 = YES. The program will create the Software\Microsoft\Windows\CurrentVersion\Run\Windows11DragAndDropToTaskbarPartialFix registry key. //0 = NO. The program will delete the existing autorun registry key if it exists. AutomaticallyRunThisProgramOnStartup=1

//Should the program show the console window when it starts? //1 = YES. A console window will be shown on program start. //0 = NO. The program will start invisibly and no extra window will pop-up. ShowConsoleWindowOnStartup=0

//Should the program print the debug information? //1 = YES. If ShowConsoleWindowOnStartup=1 the program will print a lot of messages about the actions done. //0 = NO. The program won't show any debug information and run as fast as possible (recommended). PrintDebugInfo=0

//Should the program use a fix for an issue where sometimes incorrect icons are hovered on the taskbar? This bug usually occurs after the computer wakes up from Sleep Mode, connecting or disconnecting secondary screens, or plugging out the laptop charger. The fix opens the self-created window for around 100 milliseconds, forcing the taskbar window to update and return the correct RECT. //1 = YES (recommended). //0 = NO. It's a high chance that you will experience the issue mentioned above. UseFixForBugAfterSleepMode=1

//Should the program show the Tray Icon in the system tray? //1 = YES. The program will show a Mona Lisa Megan Fox tray icon with options: Check for updates, Read the changelog, Configure, Open program folder, Restart, Quit. //0 = No. The tray icon of the program will not be created. You will have to manually kill the Windows11DragAndDropToTaskbarFix.exe by the Task Manager in case you want to terminate the program. ShowTrayIcon=1

//Should the program use ver. 1.2.0+ improvements that remove all previous limitations? //1 = YES (highly recommended). The program will use the new advanced Win+T method that works for all taskbar icons. //0 = NO. The program will use the old behaviour where it's limited to the frist 10 icons on the taskbar and is generally bad. UseTheNewBestMethodEver=1

//Should the program automatically open the first active window under the cursor, except pinned apps with no active window? //2 = LIMITED. Open only if no more than 1 window is visible under the icon. //1 = ALWAYS. Always open the first window under the icon, even when there are multiple windows under it. //0 = NEVER. Never open the first window under the icon, only show the preview thumbnails. AutoOpenFirstWindowInBestMethodEver=2

//For how long (in milliseconds) should the left or the right mouse button be clicked before the program starts checking if the mouse cursor is currently in the task bar area. HowLongLeftMouseButtonPressedBeforeContinueMilliseconds=750

//For how long (in milliseconds) should the mouse cursor be hovered over the same icon on the taskbar in order to restore its window. HowLongKeepMouseOverAppIconBeforeRestoringWindowMilliseconds=200

//Options available when UseTheNewBestMethodEver=1: //Sleep time (in milliseconds) between simulating different keyboard keys. HowLongSleepBetweenDifferentKeysPressMilliseconds=10

//Sleep time (in milliseconds) between simulating the same keyboard keys. HowLongSleepBetweenTheSameKeysPressMilliseconds=0

//Sleep time (in milliseconds) after opening the first window under the icon. HowLongSleepAfterAutoOpenFirstWindowMilliseconds=100

//Delay (in milliseconds) before opening the first window under the icon. Only if AutoOpenFirstWindowInBestMethodEver is 2 or 1. HowLongKeepMouseOverAppIconBeforeAutoOpeningMilliseconds=550

//Timeout (in milliseconds) after which the program interrupts the loop where it's detecting for the preview window changes. It's to avoid opening pinned apps with no active window. It can be a greater value, because it's a non-blocking loop which usually breaks much quicker. PreviewWindowChangeDetectionMaxMilliseconds=1000

//Remapping keys used by the program in order to simulate hotkeys //Since version 1.8 it's possible to configure the program to use different keyboard keys than default ones. It's useful for example in the case described in issue #17, where a user manually remapped his keyboard after damaging some of keys with a coffee spill. //Please read the Virtual-Key Codes article at docs.microsoft.com to find the right values (0x...). REMAP_VK_LWIN=0x5B REMAP_VK_MENU=0x12 REMAP_VK_TAB=0x09 REMAP_VK_LCONTROL=0xA2 REMAP_VK_LSHIFT=0xA0 REMAP_VK_LEFT=0x25 REMAP_VK_RIGHT=0x27 REMAP_VK_UP=0x26 REMAP_VK_DOWN=0x28 REMAP_VK_RETURN=0x0D REMAP_VK_D=0x44 REMAP_VK_T=0x54

//Less important options //You can skip the options below. They're only used to change the main thread sleeping times or default icon sizes. DefaultSleepPeriodInTheLoopMilliseconds=100 SleepPeriodWhenLeftMouseButtonIsPressedInTheLoopMilliseconds=25 SleepPeriodWhenMouseIsOnAppIconInTheLoopMilliseconds=10 DefaultTaskbarIconWidth=44 DefaultTaskbarIconHeight=48 DefaultShowDesktopButtonWidth=20 DefaultSingleWindowPreviewThumbnailWidth=250 DefaultSingleWindowPreviewThumbnailHeight=250

//Should the program monitor file Windows11DragAndDropToTaskbarFixConfig.txt for changes? //1 = YES. When you save changes to the configuration file, the program will ask you to restart itself. //0 = NO. The program won't check for the configuration file changes. ConfigFileChangeTimeMonitorAllowed=1

//Should the program use an alternative tray icon, modified by QuestYouCraft? //1 = YES. A different tray icon with a hand drag gesture will be used. //0 = NO. The default Mona Lisa Megan Fox icon will be used. UseAlternativeTrayIcon=0

Edit : to test, I deleted the .txt file and created it again. The window is not displayed anymore. In fact my configuration file exists since a few versions and I had never modified it, I do not know if it is a cause but it is solved. Thanks

[HerMajestyDrMona]

I think I know what the problem was. The description of variables: //Should the program print the debug information? //1 = YES. If ShowConsoleWindowOnStartup=1 the program will print a lot of messages about the actions done.

Maybe it updated it based on this line. Theoretically it should ignore lines with // in front, so it needs to be checked :)

[HerMajestyDrMona]

Hi again. I tested the config file that you pasted, and it still wasn't displaying the console window on start. So the // detection works fine. It was something very strange and rare, but I'm glad you managed to fix it.

For the future, I would recommend to follow the CONFIGURATION

You don't need to add all variables to your configuration file. Please only add the ones you need. The program will use the same default values as present after Variable=Value listed below.