[Bug] C:\Users\<username>\cmder\vendor\conemu-maximus5 was unexpected at this time
JimmyHodgson opened this issue · 2 comments
Version Information
Cmder version: 1.3.25.328
Operating system: Windows 11Cmder Edition
Cmder Full (with Git)
Description of the issue
When I launch the executable the app loads but has this message at the top of the screen every time. It started on an existing install after a click update i believe and now it persists even after I completely deleted the old folder and reinstalled fresh from download.
Any help is appreciated.
Thanks!
How to reproduce
No response
Additional context
No response
Checklist
- I have read the documentation.
- I have searched for similar issues and found none that describe my issue.
- I have reproduced the issue on the latest version of Cmder.
- I am certain my issues are not related to ConEmu, Clink, or other third-party tools that Cmder uses.
I just downloaded fresh and it works for me.
Run vendor\bin\cmder_diag.cmd provide the text output.
Below is the content of my config folder immediately after first launch after a fresh download.
C:\Users\vagrant\Downloads\cmder
λ dir "%CMDER_ROOT%\config"
Volume in drive C is Windows
Volume Serial Number is A07D-3A22
Directory of C:\Users\vagrant\Downloads\cmder\config
09/22/2024 09:40 PM <DIR> .
09/22/2024 09:23 PM <DIR> ..
09/22/2024 09:40 PM 3,990 clink.log
09/22/2024 09:26 PM 4 clink_errorlevel_1144.txt
09/22/2024 09:40 PM 4 clink_errorlevel_1E64.txt
09/22/2024 09:26 PM 4 clink_errorlevel_C70.txt
09/22/2024 09:23 PM 4 clink_errorlevel_CC8.txt
09/22/2024 09:26 PM 57 clink_history
09/22/2024 09:40 PM 0 clink_history_7780
09/22/2024 09:40 PM 0 clink_history_7780.removals
09/22/2024 09:21 PM 814 clink_settings
09/22/2024 09:21 PM 2,477 cmder_prompt_config.lua
09/22/2024 09:21 PM <DIR> profile.d
09/22/2024 09:21 PM 887 Readme.md
09/22/2024 09:36 PM 55,110 user-ConEmu.xml
09/22/2024 09:21 PM 682 user_aliases.cmd
09/22/2024 09:21 PM 740 user_profile.cmd
14 File(s) 64,773 bytes
3 Dir(s) 16,701,837,312 bytes free
My guess is you may have something funky in your environment that is messing something up.
It used to work i'm not sure why it broke at some point but yeah it might be something funky with my setup, here's the log file after running cmder_diag.cmd.
Thanks for the help!