After some M$ Windows updates Cygwin mintty (desktop shortcut installed by setup-x86_64.exe) starts but ends immediatelly. I tried to install all missing DLL's which can be observed with dependency walker. I installed 2012 and 2008 Microsoft Redistributable packages which were missed on My Windows 7. I installed both builds (x86 and x64). But it didn't help me to get my CygWin back, because as far as I can see from mintty's logs there is a security issue. I've got a log with the only row:
This account is currently not available.
I tried to create passwd file with CygWin's mkpasswd and with this command:
getent passwd %USERNAME%
It didn't help also and I don't have any ideas what to do next.
Now I've got a CygWin installation (Cygwin DLL 2.9.0) with mintty ends immediatelly. I can run Cygwin.bat and use the most of CygWin's functionality, but mintty is more comfortable than M$ Connhost and I want it back.
Something have happened, but today, after an ordinary reboot, mintty begun working.
P.S. It has begun after "Definition Update for Windows Defender - KB915597 (Definition 1.253.822.0)" and ended after "Definition Update for Windows Defender - KB915597 (Definition 1.253.973.0)".
Related
I have WSL 2 installed and running well and I am trying to install VSC to debug my code.
I already use (and have installed) Visual Studio Code on Windows 10.
The first thing I did was to install the .deb package provided on VSC (sudo apt install ./code_1.46.1-1592428892_amd64.deb. Everything went fine. When running code . I was prompted with
To use VS Code with the Windows Subsystem for Linux, please install VS Code in Windows and uninstall the Linux version in WSL. You can then use the 'Visual Studio Code' command in a WSL terminal just as you would in a normal command prompt.
I proceeded to uninstall VSC from my Ubuntu with sudo apt-get purge code and now I am a bit stuck.
On Windows side I installed the Remote - WSL extension and Remote Development on the existing VSC installation, but now I cannot launch it from WSL.
Any workaround?
Later edit : I know it might sound dumb, but it works by just closing all instances of WSL bash and starting all over again. Now I just have the curiosity of what did I install and what did I uninstall? And why is this non persistant?
when you run code . from inside WSL it should install a small vs code server in your home directory (~/.vscode-server) and then lunch vs code. If that doesn't work post the error message.
I'm trying to set up a web development environment using a guide on Medium. The author says we need to install Git for both Windows and for Windows Subsystem for Linux. Git takes up a lot of space. Do we need to install it twice?
I have Visual Studio Code and Ubuntu (WSL). I also installed Git for Windows 10.
Git For Windows differs from the Linux Git.
So, if you want to execute commands in a Windows CMD and a Linux WSL shell, then yes, you would need to install both.
On Windows side, that can mean simply uncompressing the self-extracting archive PortableGit-2.22.0-64-bit.7z.exe anywhere you want, and add it to your PATH.
so the new windows subsystem (2019 Windows 10 April Release) for Linux is out and my ubuntu subsystem was upgraded.
I'm supposed to be able to open the Linux folder in my windows explorer but I'm not getting the correct folders when I run the command.
falieson#firefly:~$ explorer.exe ~/
Opens the windows user's My Documents folder.
falieson#firefly:~$ explorer.exe .
Opens C:\Windows\System32
My only guess is that when I did the windows install for GitHub desktop and opted into a Linux-ification of my shell it borked this upgrade from Windows.
Thanks for your ideas to resolve this.
This is currently not possible as mentioned in JosefZ comment.
If you have the latest Windows Insider Preview, or you can wait until the next Windows release, that changes as described in the WSL Blog
Okay so I am deploying a program via SCCM 2012 to all of our laptops at our corporate office. I have the program for the package install with administrative rights so it is running under the SYSTEM account. This works perfectly on all of our Windows 7 PC's, however all of my Windows 8.1 laptops/tablets are returning error code -3 to SCCM. This means the required data was not found in the setup.iss file. I did some testing and ran the batch file that is kicking all of this off with PSEXEC -s on a windows 7 machine and it exited with code 0, so a successful install as I had expected. When I run this same test on a Windows 8.1 machine it exits with code -3 just as I was seeing in my SCCM console. I tried to recapture a new setup.iss by recording the install on that windows 8.1 machine and used that .iss in the PSEXEC test and got the same result. The kicker is that if I open an elevated command prompt and kick off the batch the program installs! So there seems to be something different with how the SYSTEM account is handling this batch file in Windows 7 vs Windows 8. Has anyone else seen something like this or have any idea why it would be failing when run as SYSTEM only on Windows 8.1?
I've been trying to install VS 2015 Community on my main computer. It is running under Windows 10 which I upgraded to a few months ago from Windows 7 Home Premium. Now I also have VS 2012 Express installed if that is a neccessary information.
However everytime I try run the vscommunity.exe to install VS 2015 I get this error message:
Translated this basically means:
This program requires a newer version of Windows
Sorry I can only get this message in German.
Hellu again.
I found a solution to the problem. So first I could've tried starting it as administrator ^^. This brought up the vs installation window.
When the installation came up it showed me the error "Setup Blocked" and told me to restart the computer. Obviously I have done this before so this couldn't be the solution. Thanks through this post I found out that I needed to turn off hibernation and then restart the computer to fix it.
To turn off hibernation just open the command line and type:
powercfg.exe /hibernate off
And to turn it back on again:
powercfg.exe /hibernate on
After restarting the installation worked correctly.
Turning off hibernation also worked for me
Cmd: powercfg.exe /hibernate off
Complete the installation and then to turn it back on again:
Cmd: powercfg.exe /hibernate on