Why I might suddenly get persmission denied when I just open TortoiseHG? - windows-7

I installed TortoiseHG 5.6.1 (x64) on guest Win 7 Ultimate x64 in VirtualBox. The host OS is Win10 Enterprise x64. When I right-click in any folder and select "Hg Workbench", it opens successfully. After that, I accidentelly deleted the *.vdi file and had to reinstall both OS and TortoiseHG again. But, this time when I right-click and select "Hg Workbench" I always get this error:
I tried older TortoiseHG versions, but I get the same error. I even tried to reinstall guest OS again, but it didn't help. I just installed OS and TortoiseHG, so what can be that I did accidentally the first time and/or other times?
UPDATE 1
I installed TortoiseHG 5.6.1 (x64) on guest Win 10 x64 in VirtualBox and I didn't get that error message. So, it has to be something with Win 7. What can that be?

Related

Can't install Windows Terminal

I can't install the windows terminal on my laptop from the Microsoft store.
Error: Try again later, something happened on our end.
Tried installing with App installer, nothing happened after clicking install. I run the store app troubleshooter, and also tried running wsreset.
I am running windows 10 home (21H1) 32 bit.
enter image description here

Xamarin Pair to Mac - Couldn't connect - Access to path is Denied

I recently wiped my Macbook Pro and I am trying to setup the "Pair to Mac" functionality in Visual Studio 2019 on my Windows machine. I also just updated Visual Studio 2019 on my Windows machine to 16.3.0. The Mac is running Visual Studio 8.3 (build 1805).
I receive an error when I try to Pair to Mac:
Couldn't connect to [ip address]. Please try again. XMA-Failed-dd7e7bf-Access to path '/Users/[user]/.config/Xamarin/Xamarin Messaging/1.1.6.217-d16-3+64904be' is denied.
I have Remote Login enabled, Firewall is off, Xcode 11 installed, xamarin-ios sdk installed.
It looks like a permissions issue but I'm not sure what else to check.
Edit
I'm also able to ssh into the Mac and run a successful 'ls' command.
I ran the following command and it fixed my issue:
sudo chown -R [username] .config

CygWin mintty.exe (x64) ends immediately on WIndows 7 (64)

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)".

Xamarin Android Player Error when attempting to find VirtualBox

I have a clean install of Windows 10. After installing Visual Studio 2015 and Xamarin Bussiness edition I installed Xamarin Android Player x64 and now I receive the following error:
Error when attempting to find VirtualBox please check it's installed and try again.
Xamarin Android Player will now exit.
A solution is referenced in Xamarin fourms stating
Fixed it by adding "C:\Program Files\Oracle\VirtualBox" to my %PATH%
I am able to open VirtualBox version 4.3.28 r 100309 without issue.
How do I implment this solution or is there a newer solution?
I am running Windows 10 Professional and did a clean installation. Had the same problem. I opened the environment variables and the "VBOX_MSI_INSTALL_PATH" was set to:
C:\Program Files\Oracle\VirtualBox\
I changed it to
C:\Program Files\Oracle\VirtualBox
and it worked for me.. (notice the last backslash)
Thanks .. Ragnar Kofi Billy Force on facebook
Try installing the Latest version of Virtual Box, Since v5.0 has fixes for Windows 10
http://download.virtualbox.org/virtualbox/5.0.4/VirtualBox-5.0.4-102546-Win.exe
Changelog: https://www.virtualbox.org/wiki/Changelog
Windows hosts: fixed crash when opening Windows dialogs from the VM process on Windows 10 (bug #14351).
Windows hosts: fixed host-only adapter creation issues on Windows 10 (bug #14040)
Windows hosts: fixed audio on Windows 10 (bug #14432).
Windows Additions: fixed a potential crash in the WDDM driver with Windows 10 (bug #14190).
VRDP: allow Windows 10 RDP clients (bug #14216).
Windows hosts: fix for Windows 10 build 10525 and later (bug #14502).
Windows hosts: fixed network adapter enumeration on Windows 10 (bug #14437).
VMM: fixed an issue with Windows 10 guest kernel debugging over the network for Hyper-V paravirtualized VMs.
I have a same problem too and installing the latest version has fix it
Add VirtualBox to your system environment PATH variable.
None of the other answers helped me. The Android Player installer was forcing the install of Virtual Box 5.0.4 which was not working on Windows 10 Home (build 14393.51).
What did work for me was to install the latest virtual box (version 5.1.2 r108956) after installing Android player. While I can't start the android devices from Virtual Box's manager, I have had no problems starting them from Android Player or Visual Studio.
Just run as admin (Right hand click on desktop shortcut)

Vmware Workstation 11 installation MSI failed in Windows 8.1

I get a MSI failed message every time when I install Vmware Worksatation 11 on my windows 8.1 computer. I've tried to clear previous temp data but it doesn't work.
Thanks.
I have the same problem and have fixed it.
Try to disable Hyper-V on Control Panel >>> Programs >>> Turn windows features on or of >>> Unselect Hyper-V >>> Click Ok and restart your computer
If you attempt a VMware Workstation 11 install, and it fails part-way through, a reboot typically addresses the install failure. If not, can you:
post some more information about what the error is
post the %TEMP%\vmsetup*.log files from your failed install attempt

Resources