Existing issues matching what you're seeing
Git for Windows version
git version 2.55.0.windows.5
cpu: x86_64
built from commit: 32c4f7689275d233577576630e1ac5b7eb354eb0
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
rust: disabled
feature: fsmonitor--daemon
gettext: enabled
libcurl: 8.21.0
OpenSSL: OpenSSL 3.5.7 9 Jun 2026
zlib: 1.3.2
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
default-ref-format: files
default-hash: sha1
Windows version
Windows 11
Windows CPU architecture
x86_64 (64-bit)
Additional Windows version information
Microsoft Windows [Version 10.0.26200.9168]
Options set during installation
Editor Option: VIM
Custom Editor Path:
Default Branch Option:
Path Option: Cmd
SSH Option: OpenSSH
Tortoise Option: false
CURL Option: WinSSL
CRLF Option: CRLFAlways
Bash Terminal Option: MinTTY
Git Pull Behavior Option: Rebase
Use Credential Manager: Enabled
Performance Tweaks FSCache: Enabled
Enable Symlinks: Disabled
Enable FSMonitor: Disabled
Other interesting things
No response
Terminal/shell
Git Bash
Commands that trigger the issue
Any command that brings up Vim with a pre-existing commit message or other editable file, such as:
git commit --amend
git cherry-pick --continue
git rebase -i
Expected behaviour
Vim should be pre-populated with the existing commit message (in the case where a commit message is being edited) or the complete list of existing commits (in the case of an interactive rebase). Vim should be in Normal Mode. The first line (i.e. the commit message subject or the first commit to be rebased) should not be blank or missing. The colours should be the usual ones.
See this screenshot from version 2.55.0.windows.4 for expected behaviour:
Actual behaviour
The behaviour is random and intermittent. The following can occur, sometimes more than one at a time:
- Sometimes the first line is blank/missing.
- Sometimes Vim is in Insert mode unexpectedly.
- Sometimes the colours of the various components are different from usual.
- Sometimes the first line is replaced with the string
;rgb:0000/0000/0000.
- Sometimes the first line is replaced with the string
;rgb:bfbf/bfbf/bfbf.
See these screenshots for some examples:
Repository
This behaviour is observed in every repo.
Existing issues matching what you're seeing
Git for Windows version
Windows version
Windows 11
Windows CPU architecture
x86_64 (64-bit)
Additional Windows version information
Options set during installation
Editor Option: VIM Custom Editor Path: Default Branch Option: Path Option: Cmd SSH Option: OpenSSH Tortoise Option: false CURL Option: WinSSL CRLF Option: CRLFAlways Bash Terminal Option: MinTTY Git Pull Behavior Option: Rebase Use Credential Manager: Enabled Performance Tweaks FSCache: Enabled Enable Symlinks: Disabled Enable FSMonitor: DisabledOther interesting things
No response
Terminal/shell
Git Bash
Commands that trigger the issue
Any command that brings up Vim with a pre-existing commit message or other editable file, such as: git commit --amend git cherry-pick --continue git rebase -iExpected behaviour
Vim should be pre-populated with the existing commit message (in the case where a commit message is being edited) or the complete list of existing commits (in the case of an interactive rebase). Vim should be in Normal Mode. The first line (i.e. the commit message subject or the first commit to be rebased) should not be blank or missing. The colours should be the usual ones.
See this screenshot from version 2.55.0.windows.4 for expected behaviour:
Actual behaviour
The behaviour is random and intermittent. The following can occur, sometimes more than one at a time:
;rgb:0000/0000/0000.;rgb:bfbf/bfbf/bfbf.See these screenshots for some examples:
Repository
This behaviour is observed in every repo.