PlugInstall threw "not an editor command" on Windows
I followed the instruction to install vim-plug and created a minimal config file _vimrc_temp (only 3 lines)

then started Vim with vim -u .\_vimrc_temp.
It prompted "Press ENTER or type command to continue" (no other message).
Then I pressed ENTER and executed :PlugInstall and it raised not an editor command:

The whole config file:
call plug#begin()
Plug 'junegunn/vim-easy-align'
call plug#end()
I also tried some paths like:
call plug#begin(glob('~\vimfiles\plugged'))
call plug#begin(glob('~/vimfiles/plugged'))
environment
VIM - Vi IMproved 9.0 (2022 Jun 28, 编译于 Sep 14 2022 22:03:49)
MS-Windows 64 位控制台版本
包含补丁: 1-467
编译者 appveyor@APPVYR-WIN
巨型版本 无图形界面。 可使用(+)与不可使用(-)的功能:
+acl +ex_extra +multi_lang -tag_any_white
+arabic +extra_search +mzscheme/dyn -tcl
+autocmd -farsi -netbeans_intg +termguicolors
+autochdir +file_in_path +num64 +terminal
+autoservername +find_in_path +packages -termresponse
-balloon_eval +float +path_extra +textobjects
+balloon_eval_term +folding +perl/dyn +textprop
-browse -footer +persistent_undo -tgetent
++builtin_terms +gettext/dyn +popupwin +timers
+byte_offset -hangul_input -postscript +title
+channel +iconv/dyn +printer -toolbar
+cindent +insert_expand +profile +user_commands
+clientserver +ipv6 +python/dyn +vartabs
+clipboard +job +python3/dyn +vertsplit
+cmdline_compl +jumplist +quickfix +vim9script
+cmdline_hist +keymap +reltime +viminfo
+cmdline_info +lambda +rightleft +virtualedit
+comments +langmap +ruby/dyn +visual
+conceal +libcall +scrollbind +visualextra
+cryptv +linebreak +signs +vreplace
+cscope +lispindent +smartindent +vtp
+cursorbind +listcmds +sodium/dyn +wildignore
+cursorshape +localmap +sound +wildmenu
+dialog_con +lua/dyn +spell +windows
+diff +menu +startuptime +writebackup
+digraphs +mksession +statusline -xfontset
-dnd +modify_fname -sun_workshop -xim
-ebcdic +mouse +syntax -xpm_w32
+emacs_tags -mouseshape +tag_binary -xterm_save
+eval +multi_byte_ime/dyn -tag_old_static
系统 vimrc 文件: "$VIM\vimrc"
用户 vimrc 文件: "$HOME\_vimrc"
第二用户 vimrc 文件: "$HOME\vimfiles\vimrc"
第三用户 vimrc 文件: "$VIM\_vimrc"
用户 exrc 文件: "$HOME\_exrc"
第二用户 exrc 文件: "$VIM\_exrc"
defaults 文件: "$VIMRUNTIME\defaults.vim"
编译方式: cl -c /W3 /GF /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE -DFEAT_TERMINAL -DFEAT_SOUND -DF
EAT_JOB_CHANNEL -DFEAT_IPV6 -DHAVE_SODIUM -DDYNAMIC_SODIUM -DDYNAMIC_SODIUM_DLL=\"libsodium.dll\" /I "C:\libsodium\include" -DWINVER=0x0501 -D_WIN32_WINNT=0x0501 /source-charset:utf-8 /MP -DHAVE_STDINT_H /Ox /GL -DNDEBUG /Zl /MT /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_LUA -DDYNAMIC_LUA -DDYNAMIC_LUA_DLL=\"lua54.dll\" -DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\"python310.dll\" -DFEAT_MZSCHEME -I "C:\racket\include" -DMZ_PRECISE_GC -DDYNAMIC_MZSCHEME -DDYNAMIC_MZSCH_DLL=\"libracket3m_da32rk.dll\" -DDYNAMIC_MZGC_DLL=\"libracket3m_da32rk.dll\" -DFEAT_PERL -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl532.dll\" -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RUBY_DLL=\"x64-msvcrt-ruby300.dll\" -DRUBY_VERSION=30 -DFEAT_HUGE /Fd.\ObjCULYHRZAMD64/ /Zi
链接方式: link /nologo /opt:ref /LTCG oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib comdlg32.lib ol
e32.lib netapi32.lib uuid.lib user32.lib /machine:AMD64 libcmt.lib /nodefaultlib:lua54.lib /STACK:8388608 /nodefaultlib:python27.lib /nodefaultlib:python310.lib winmm.lib WSock32.lib Ws2_32.lib /PDB:vim.pdb -debug
- Type:
- [x] Bug
- [ ] Enhancement
- [ ] Feature Request
- [ ] Question
- OS:
- [ ] All/Other
- [ ] Linux
- [ ] macOS
- [x] Windows
- Vim:
- [x] Terminal Vim
- [ ] GVim
- [ ] Neovim
got the same error with gvim. Anyone know how to fix it?
It prompted "Press ENTER or type command to continue" (no other message).
You can check the previous error messages with :messages command.
This is still not working at all on Windows in 2024. Literally following the exact instructions on the webpage results in this error. Is it just not going to be addressed?
Works for me just fine. FWIW, a common mistake on Windows is to put the plug section in gvimrc instead of vimrc.
You should check if Vim is properly loading the autoload files by examining the output of :scriptnames.
It also happend in my device