Hello everyone, Thanks for your input. I'm using Windows 10 20H2 - OS Build 19042.985. As for the org version, I hit this issue even when running it out of the box. I download the emacs-27.2-x86_64 zip file, extract it, cd to the bin directory and run '.\emacs.exe -Q'. When I C-x C-f test.org (a new file) it hangs briefly and outputs 'shell command succeeded with no output' and the issue persists. Running M-x org-version it outputs 'Org mode version 9.4.4 (release_9.4.4 @ c:/Users//OneDrive/Desktop/emacs-27.2-x86_64/share/emacs/27.lisp/org/'. If I run M-x org-mode or open a new org file after the first one it works just fine. Is there perhaps a different set of windows binaries I should be using? Or is there a way to run a stack trace on the entire emacs session? It's not running into any actual error so debug isn't yielding anything. All good things, Aaron On Fri, May 21, 2021 at 10:08 AM Shibu N.V wrote: > Hello Aaron, > I think, the Issue is specific to the version of Windows. > I faced the issue with Windows 10,1903. When I updated to Windows 10 20H1, > it resolved itself. > > > N.V.Shibu > Assistant Professor Senior Grade > Sri Ramakrishna Institute of Technology > Coimbatore-10. > > > On Fri, May 21, 2021 at 1:39 PM Aaron wrote: > >> Hi folks, >> >> >> >> I upgraded emacs from 26.3 to 27.2 and am encountering this same issue on >> Windows 10. >> >> I’ve tried using org 9.4.4 and 9.6 as well and also using emacs 27.1 but >> no dice. >> >> This has all been done with a ‘clean’ install – wiped my .emacs file and >> .emacs.d directory. >> >> I get the issue when I open any org file or even if I create a new file >> ending in .org. >> >> Any other ideas on how to get it working? >> >> >> >> All good things, >> Aaron >> >