On Windows, install.bat keeps trying to run some program that can't run on...
Free GNUWin32 utility packages
Status: Beta
Brought to you by:
michaelis
Menu
▾
▴
#32 On Windows, install.bat keeps trying to run some program that can't run on Windows, creating a chain of events forcing me to power off my computer and restart it
I was installing GetGnuWin32, and ran install.bat after running download.bat. Install worked great until it was trying to "clean up" like, I think, manifests and stuff. The Windows 10 OS kept popping up this modal window saying "This program cannot be run on your computer". I would say OK, but it would pop right back. This window is modal for the entire OS; while it is up, I cannot do anything else. This modal window kept popping up over and over again. After pressing OK 20 times, I powered off my computer, because how else was I going to use it?
It appears install.bat is persistent in trying to run the program, which caused that system modal window to pop up, and hosing my computer session. This is bad, you guys. Please fix it.
Did it happen it before or after the supplemental install prompt? I can't reproduce this in Windows 10 (build 1703 (15063.332)). I have reviewed the loop section of the code and I don't see what could be causing it. Only two non-native utilities are called, bin\test and bin\unzip. If you run either of those utilities on their own do you see the same messsage?
I just experanced this today when I tried to install on a clean install. I used procmon to try and track down what was failing. So this process became strange to me, the processes I see looping looping is:
GetGnuWin32\gnuwin32\bin\install-info.exe
I hope this helps you. I'll happily provide any other issistance if you need.
Also it's after the supplemental install finishes.
install-info should run multiple times, so that is not unusual. If you click on that file, do you see the same "This program cannot be run"?
Not reproducible, closing
This is indeed an open bug. I can reproduce it on my Windows 10 Pro x64 machine which is running off of an Alienware 17 R5. I get the error after install.bat starts up the "Finished with packages. Fixing manifests and info entries..." process.
I'm running Microsoft Windows 10 Pro version 1803 (OS Build 17134.23) and I can confirm that this bug is present.
I can confirm that just running install-info.exe re-produces the problem.