Hi,
After the one year anniversary update I get error opening a ksh shell sh.exe:"_main: memory allocation error during startup."
Anyone else see something like this?
Thanks,
Keith
Tap F8 just before you would usually see the Windows flag appear on startup. Select "Safe Mode with Networking". Does it still fail to start?
If it does not, right click your start button, select Command Prompt (Admin) and type "sfc /scannow" then reboot.
If it doesn't start, or gives you the same error, reboot the computer again and select "Startup Repair" then follow the prompts.
Post back with how it goes.
Andrew
[Safe Mode with Networking]
Window pops up reading: Get Started this app can't be opened with build-in admin account.
Clicked <ok>
The shell open behaves same.
<cmd>[sfc /scannow - reboot]
"Windows Resource Protection did not find any integrity violations."
The shell open behaves same.
[start-up repair]
The shell open behaves same.
This is a clean install of Win 10 Pro. and ksh open worked. the anniversary update caused the failure with shell.
The ksh open may or may not occur in error; whether opened in error or not the shell window suffers at times with the prompt:"_main: memory allocation error during startup." when ever you enter commands. It's broken.
Are you using the latest insider build? Or are you using the public 14393.xx build? There is a known issue in the latest insider (14915) that causes the bash shell to stop working, you need to uninstall and reinstall it from Programs & Features. Or are you using git-bash?Hi,
After the one year anniversary update I get error opening a ksh shell sh.exe:"_main: memory allocation error during startup."
Anyone else see something like this?
Thanks,
Keith
I'm using the public updater. The anniversary update is a major step, takes twice as long as the windows 12 pro install. The A update recreates windows dir; If the insider build is needed, should I just re-start the install from 0 (clean re-install of windows 10 pro and then update via insider build).
Bash is also used on this pc but employs mintty; it is not affected by the A build. The ksh uses a window like that of cmd in dos utilities. ksh is the program that is now broken upon A build.
The A build alters permissions/ownership of windows dir, ksh uses utils in windows/system32. In windows 7 ownership of windows dir was taken from trusty and given to this user.
The goal is to molest windows 10 as little as possible and continue to use ksh on it.
I would wait for an update. You could try a refresh, and open the permissions of your whole Windows folder to everyone to see if it makes a difference (the memory allocation error could be privilege related - sh.exe could need a resource that it no longer has permission to access or execute) but the most likely problem is a file update making problems in the expected memory addresses sh.exe references, and sh tries to put something in space that is now in use.
Only the devs of ksh or sh can fix that.
Well, I wish I knew a way to make this happen; we can alter number of buffers and buffer size; neither of which were alter B/W 10 and the A update. Maybe I should take ownership of windows as in windows 7.
OK, trying to take ownership of the windows dir appeared to be the wrong direction after a little effort to do so. Aborted this and recovered from a restore point (trouble was expected).
So things are just as they were, broken: ksh will intermittently work and fail with error message "_main: memory allocation error during startup."
