Why can't I start the Virtual Machine I just built using VitrualBox? - windows-10

Everything used to work fine, but I haven't been using Virtual Box for several weeks. Now all of the sudden, I get the following exception when trying to start my Windows 10(32-Bit) VM. Note - Things were working fine several weeks ago. As far as I can tell, I haven't changed anything on my system that would cause this. The exception details are as follow:
VirtualBox - Error In supR3HardenedWinReSpawn (rc=-5640)
Please try reinstalling VirtualBox. where supR3HardenedWinReSpawn
what: 1 VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification
Failure: The process has more than one thread
I have been researching this for some time, to avail. Any help would be greatly appreciated.

There is a workaround:
Open VMbox manager
Run your VM with option "Detachable start"
Wait a while and then use "Show" to show the screen
Detachable start option
Show the screen
My setup:
Oracle VM Box 6.0 running on Win10,
VM is Ubuntu 18.04

If you are using vagrant to boot up your Virtual machine, then in most cases the error is due to improper shutdown of the VM. A fix that worked for me is to execute vagrant halt or similar commands multiple times until you have a clean boot.

In case anyone is in the same predicament, I will share what finally fixed my issue. I found a post during my hours and hours of searching that said you have to enable virtualization in BIOS settings. I checked my machine and virtualization was enabled, so I went on searching. At a loss for what to try next, I finally tried turning virtualization off, just to see. No change, but when I went to turn it back on, just as a flook I turned Turbo off, and what do you know - All of the suddent I can start my VM. So the solution, in case it saves someone time:
Uninstall Virtual Box (Latest Version)
Reboot your machine and enter BIOS
Make sure anything with the term 'Virtualization' is turned on
Make sure anything with the term 'Turbo' is turned off
Reboot your machine
Install Virtual Box
Hopefully this saves some poor soul what I had to go through to get this thing working.

METHOD A
If you are using WindHawk, exit it and re-try.
Method B
download previous version from https://www.virtualbox.org/wiki/Download_Old_Builds
install & extensions
Try to re-run your guest OS.

Try to do these steps:
1. Uninstall the VirtualBox program.
2. In your C:\users\\ might have two folders called ".VirtualBox" and "VirtualBox VMs": Delete them
3. Restart your PC
4. Install VirtualBox again
5. Add again your VM
6. It must working fine!
These steps worked for me!

Workaround 1:
Just increase the RAM size from virtual box settings
Right Click on OS image .
Settings->System->MotherBoard
Increase the base memory
Workaround 2:
Change the Paravirtualization Interface from default to none
Right Click on OS image .
Settings->System->Acceleration
Change acceleration from default to none.
The above one's was basically a workaround , which can work in some but not in all.
The best thing would be to reinstall virtual box with latest version which virtual box has tried to rectify the bug and use the same vdi files which was made by Virtual Box .

One of the most common causes that will cause this type of behaviour is a missing driver (VBoxDrv.inf). It’s possible that due to some permission issues, the installation of this crucial driver doesn’t complete during the initial installation. In this case, you can fix the problem by installing the VBoxDrv.inf manually.
1.Fix the directory problem Press Windows key + R to open up a Run dialog box. Inside the text box, type ‘regedit’ and press Enter to open up Registry Editor. When you’re prompted by the User Account Control (UAC), click Yes to grant admin access.
Once you’re inside the Registry Editor, use the left-hand section to navigate to the
following location: HKEY_LOCAL_MACHINE\system\currentcontrolset\services\vboxdrv
After you arrive at the correct location, move over to the right-hand section and
double-click on ImagePath the path associated should be \C:\Program
Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.sys
if not replace with the above path and click ok.
Install the VBoxDRV.inf OPen location C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv right-click on VBoxDrv.inf and choose Install from the context menu.
Then in cmd run command "sc start vboxdrv"
Restart system. This should work.

Related

Install windows updates on Azure Virtual Machine W10

I have a Windows10 Azure Virtual Machine running, and via the Windows Update Config screen (in Windows) I see several updates ready to install. However, the Update and Restart option in the start menu doesn't seem to do anything, and the same for the Restart functionality in the Virtual Machine pane of Azure.
I created an Update Management schedule (via Guest & Host Update menu), but this also doesn't seem to do anything. It succeeds after one minute, and when I look on the VM it still lists the updates as needed to install.
How can I install these updates on a Windows10 Azure Virtual Machine?
Try following the steps in this article to clear the Windows Update Cache. Then attempt installing one at a time
https://blogs.technet.microsoft.com/mckittrick/windows-update-issues-clear-windows-update-cache/
If that fails, please try the following :
Click on Start, and then click Run.
Type cmd in the Open box to get a DOS prompt.
Type "net stop wuauserv" without the quotes at the command prompt, and press
Enter.
Delete (or put in recycle bin) the contents of
C:\WINDOWS\SoftwareDistribution (but not the SoftwareDistribution folder)
Type net start wuauserv at the command prompt, and press Enter.
Now try Windows Update again.
If the issue still persists, kindly share the screenshot of the windowsupdate
Also is this the only VM where the issue is happening?

dnf.exceptions.error some packages from local repository have incorrect checksum

I am trying to install redhat (rhel8) in virtualBox 6.1 on a windows 10 64 bit Home edition machine.
I verified the checksum of the iso file after download and its correct (I compared the checksum against another friend iso file who is able to install properly), still I am getting exception like
dnf.exceptions.error some packages from local repository have incorrect checksum
I even tried to run troubleshooting, but it raise exceptin like
failed to start media check on /dev/sr0 virtualbox
I have downloaded the iso files from multiple places and every time it gives me the same exception.
Any help is highly aprreciated.
Finally I found the reason for the above error.
Virtual Box uses virtualization to run multiple Operating Systems and in one system (let's say a windows machine) only one of the application will be allowed to use system virtualization capability.
So we have to disable any manual virtualization if performed in the system.
So we can disable virtualization by following ways:
Search for “Turn Windows features on or off” in the Start menu, hit
the Enter key to open the Windows Features window. Here, scroll down
to Hyper-V and disable it by clearing checkbox next to it. Then click
OK
Disable Hyper-V by using command.
Press Windows logo key + X, then hit A to run Command Prompt as administrator. In Command Prompt window, type
bcdedit /set hypervisorlaunchtype off
and hit Enter key to execute this command.
Finally restart system.

Atom installation error on Windows 10

I was getting this error when trying to install Atom using the installer.
I tried to run as Administrator but ever having the same error.
So I opened the Setup Log and found this line in many places of the log:
Failed to load local releases, starting from scratch: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\david\AppData\Local\slack\packages\RELEASES'.
To resolve this problem, I simply tried to change the AppData folder properties, unchecking the Attribute "Read-Only" and applying to subfolders.
After that, I could install the application and everything is working well.
I don't know whether what I did was the best solution, but it fixed my problem :)
Hope this help someone
If you have anti-virus installed on your system. Please disable it and try it once. Hope this will work for you because this worked for me like a charm.
One more thing you can check that your windows update service is also running. You check it out in Task Manager ->
So do this thing and check it out.
This is a permission related issue. Could be you don't have permission to write, in that case run as Administrator.
Right Click on the installer and select Run As Administrator.
If you still have the issue, disable your antivirus, defender or whatever you have to protect your PC from threats. Once Installed Enable it BACK
if you have Dropbox opened, close it.
You can try this:
open control panel
Windows firewall
click allow an app or feature through windows firewall
In that at right bottom click allow another app
Browse the downloaded atom.exe file and click open and click ok
first uninstall or disable the antivirus. In my case Guardian net secure was handling all the things of windows firewall. so i was not able to allow the app through windows firewall. therefore, it is necessary to uninstall these. then restart your laptop.
after restarting open control panel. go to windows firewall. on left top you will see
allow an app or feature through windows firewall . click on it. dialog box appears. click on change settings. at bottom click allow another app. then browse the downloaded file atom.exe. then install it
What worked for me was closing Slack and terminating any of it's processes in Task Manager.
This was what worked for me (Windows 11):
Go to properties>compatability on the installation file. Run the troubleshooter for compatibility, and it shoul provide a solution, wait, and if it works, select that it did so, and you’re all done.
To resolve this problem, I simply tried to change the AppData folder properties, unchecking the Attribute "Read-Only" and applying to subfolders.
After that, I could install the application and everything is working well.
This worked for me on Windows 11 home version.
Hope this helps
I managed to install by finding an older version.

Unable to access Android SDK add-on list

I'm new to Android programming. I was installing the Android studio and it got stuck at one point during installation showing the following message.
So, don't to how to proceed, I searched about it, but couldn't get explanation about this specific condition.
Can someone explain what to do next?
Screenshot:
Note: I'm using Windows 7, Installed JDK 7 before installing Android studio.
Update: I tried to click upon "Setup Proxy" and then just clicked ok without doing anything and it worked, don't know how, but it did.
Try that if any one face the same.
Add the following code to C:\Program Files\Android\Android Studio\bin\idea.properties
disable.android.first.run=true
Just open the file and press Ctrl+F and type run then you will find this run=false, change it to true.
1) click on set up proxy.
2) Select option Auto Detect proxy.
3) Click continue, it will work!!
All the best
I clicked Cancel at this screen and process of setup continued. I saw it on Linux after copying android studio folder from one PC to another. By the way, I started studio not connected to Internet cause I try to be able to work offline.
I just hit this same problem - I was on a VPN.
I tried setting a proxy with 'auto detect proxy settings' but it did not help.
Then I tried disconnecting from the VPN with no proxy set - this resolved the problem for me.
good luck.
You can set the right proxy to solve this problem.
Set proxy ->
Manule...
Https and port
Sometimes,if you use Shadowsocks on your macOS, maybe you will have the same problem.You can turn Shadowsocks off to deal with this problem.
I finally solved the problem by following the Steps:
Add the following code to "C:\Program Files\Android\Android Studio\bin\idea.properties"
Open idea.properties with notepad
Then, enter the code below anywhere on a new line in the file (see attached image)
Code :
disable.android.first.run=true
Save the file
Run the application
Clear your DNS if there is any dns server settings like google, comodo,
symantec etc.
Check your firewall settings if you are using tinywall, zonealarm etc.
If your computer and network connection doesn't have any dns settings and firewall; then check your internet connection maybe there is an update process to slowing down your internet speed. So if there is a process stop or wait for it. And try again. Good luck...
Yet another reason why this can happen is when your time and date settings are not synchronized correctly. I installed android studio inside a virtual machine linux guest that didn't properly synchronize the time with the windows host and as a consequence the above message occured even though my internet connection was working fine.

Kernel debugging in VS 2012

I have a Kernel mode filter driver project. Host: Win8 Pro x64 running VS2012, Target:Win8 Pro x64 VM on the same machine. I was able to provision the VM through VS 2012 over the network. I deployed the package project. When I try to deploy and Install the package from VS, I am not able to succeed. So I manually installed the driver and the driver works fine. After installing the driver manually, I attach to the kernel of the VM and click on Break all. I find the Kd console in the immediate window of VS '12. I type the command "bu !DriverEntry" and then I type the "g" command. I see the message Debuggee is running. When I place break points on my code and press any key in the VM, I don't see the break points getting hit in my code. Need help!!
Use Fltmc command to load and attach your filter to a specific drive
You can put breakpoints directly in VS without the need to type in the console, if your filter is getting loaded after you type fltmc load "filter name" VS should stop at the driver entry function breakpoint, you may also need to attach it.
Dont forget to check if your debugger is working by when you click break all target machine should freeze.
I wasn't able to debug through VS. I went for a work around and this time I used a Win7 VM. Made use of the KdPrint() method and used the DebugView tool to see the messages. This is a lengthy process but atleast I'm able to debug my driver. Hope this helps someone else too

Resources