Virtual Box stopped running virtual drives
Virtual Box stopped running virtual drives
I have had Virtual Box for years. I am running Windows 10 (I'll leave a Speccy list at bottom). I have a Win 3.1, Win 98se, Win XP, Puppy Linux, and a couple other Linuxs as Virtual Boxes. I have various reasons for this (like I have Turbo Basic and like to run it in Windows 3.1. Yeah - I know Dorky or Geeky ). Anyway, I upgraded to v6.1.40 and this seem to have done something to the Virtual Box files. Here is the error I am getting:
The forum says no links in first post. Ok. I have the DropBox links and I will post them later. Sorry - forum rules.
What I have tried:
1. I tried uninstalling v6.1.40 and reinstalling v6.1.40
2. I tried uninstalling v6.1.40 and installing v6.1.34a
3. I tried uninstalling v6.1.34a and installing v7.0.4
4. I tried uninstalling v7.0.4 and installing v5.2.44 (See note #1 below)
5. I tried uninstalling v5.2.44 and installing v6.1.40 (See note #2 below)
6. I tried uninstalling v6.1.40 and installing v7.0.4
7. I tried uninstalling v7.0.4 and installing v6.1.34a
8. I tried uninstalling v6.1.34a and installing v6.1.14
9. I tried uninstalling v6.1.14 and installing v6.1.12
NOTE #1: I read a lot of the posts about things that can go wrong. VBoxDrv folder was not installed for v6.1.40 and v7.0.4 which is why I backed up to v5.2.44 and got the VBoxDrv folder and put it in my backup directory folder for Virtual Box (so I can't lose it again).
NOTE #2: Trying the later versions WITH the VBoxDrv folder to INSTALL the .INF file if I got the same error.
None of the above worked. From #5 on - I always tried installing the .inf file - but nothing.
Help?
The forum says no links in first post. Ok. I have the DropBox links and I will post them later. Sorry - forum rules.
What I have tried:
1. I tried uninstalling v6.1.40 and reinstalling v6.1.40
2. I tried uninstalling v6.1.40 and installing v6.1.34a
3. I tried uninstalling v6.1.34a and installing v7.0.4
4. I tried uninstalling v7.0.4 and installing v5.2.44 (See note #1 below)
5. I tried uninstalling v5.2.44 and installing v6.1.40 (See note #2 below)
6. I tried uninstalling v6.1.40 and installing v7.0.4
7. I tried uninstalling v7.0.4 and installing v6.1.34a
8. I tried uninstalling v6.1.34a and installing v6.1.14
9. I tried uninstalling v6.1.14 and installing v6.1.12
NOTE #1: I read a lot of the posts about things that can go wrong. VBoxDrv folder was not installed for v6.1.40 and v7.0.4 which is why I backed up to v5.2.44 and got the VBoxDrv folder and put it in my backup directory folder for Virtual Box (so I can't lose it again).
NOTE #2: Trying the later versions WITH the VBoxDrv folder to INSTALL the .INF file if I got the same error.
None of the above worked. From #5 on - I always tried installing the .inf file - but nothing.
Help?
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box stopped running virtual drives
That's because zip files and the forum's Upload Attachment tab cover all needs for posting logs, screenshots, etc, from the first day first post.markem wrote:The forum says no links in first post.
Error messages from Virtualbox have a Copy button that enables copying the message text to the forum, no screenshot needed.
This 'folder' doesn't ring a bell.markem wrote:VBoxDrv folder
Uninstall Virtualbox and reboot.
Go to "C:\Windows\System32\drivers", look for any files called 'Vbox*.sys' (there could be up to 5) and delete them.
Reboot again.
If you have any 3rd-party security or anti-malware software, disable the living daylights out of it for a moment.
Reinstall Virtualbox using right-click-Run-As-Administrator.
Re: Virtual Box stopped running virtual drives
Already did that many times. No VBox.sys files every time I looked.This 'folder' doesn't ring a bell.
Uninstall Virtualbox and reboot.
Go to "C:\Windows\System32\drivers", look for any files called 'Vbox*.sys' (there could be up to 5) and delete them.
Reboot again.
If you have any 3rd-party security or anti-malware software, disable the living daylights out of it for a moment.
Reinstall Virtualbox using right-click-Run-As-Administrator.
Re: Virtual Box stopped running virtual drives
Is tihs what you mean?
There is another dialog box that I can not copy. Except as a PNG file via Faststone.Failed to open a session for the virtual machine win3.1.
The virtual machine 'win3.1' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'E:\VirtualBox VMs\win3.1\Logs\VBoxHardening.log'.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box stopped running virtual drives
Yes that's a workable error code. Please zip and post that log mentioned in the message using Upload Attachment.
Re: Virtual Box stopped running virtual drives
Ok, I have five logs. VBox.log, VBoxHardening.log, VBox.log1, VBox.log2, VBox.log3. I will upload VBox.log3 as that might be the latest.
- Attachments
-
- win3.1-2022-12-09-10-52-00.log
- (25.48 KiB) Downloaded 11 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box stopped running virtual drives
scottgus1 wrote:Please zip and post that log mentioned in the message
markem wrote:More details may be available in 'E:\VirtualBox VMs\win3.1\Logs\VBoxHardening.log'.
Cue big Family Feud fail buzzer noise.markem wrote:I will upload VBox.log3
Try again.
BTW, vbox.log is the latest, then vbox.log.1, then vbox.log.2, then vbox.log.3. Set the folder view to Details, Date Modified, latest first. No need to guess.
Re: Virtual Box stopped running virtual drives
Done.
Er.....can't. File is 132KB and maximum size is 128kb. Which end do you want me to trim?
Er.....can't. File is 132KB and maximum size is 128kb. Which end do you want me to trim?
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box stopped running virtual drives
If the zip file itself is 132kB, save the hardening log as two half files and zip/post both. Please don't send a partial file.scottgus1 wrote:Please zip
Re: Virtual Box stopped running virtual drives
Argh. Did not even think about using a ZIP file. Well - here it is. Sorry - working on a new VIM syntax file.
- Attachments
-
- win3.1-2022-02-03-18-09-20.log.zip
- (26.14 KiB) Downloaded 12 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box stopped running virtual drives
You have to read more carefully. You were supposed to zip and post the hardening log.....
Try to run the VM again. (The log you posted was from February 2022, rather old.) If the hardening error message appears, zip and post the shown hardening log.
Try to run the VM again. (The log you posted was from February 2022, rather old.) If the hardening error message appears, zip and post the shown hardening log.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtual Box stopped running virtual drives
The log he posted above, claiming it was VBox.log.3, was in fact the hardening log instead.
And it shows a whole plethora of unnecessary third party AV (Kaspersky).
And it shows a whole plethora of unnecessary third party AV (Kaspersky).
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box stopped running virtual drives
Ah, I never looked at it, based on what OP called it.
markem, per Diagnosing VirtualBox Hardening Issues last paragrapgh in post 3 and post 4 re exit code 1 in the error message, the extra AV software Mpack pointed out may be getting in the way.
There are also some errors mentioned:
If the reinstall does not fix the problem, please uninstall (not disable) Kaspersky and all other "security" software, and let Windows Defender run. Try Virtualbox, and see what happens.
markem, per Diagnosing VirtualBox Hardening Issues last paragrapgh in post 3 and post 4 re exit code 1 in the error message, the extra AV software Mpack pointed out may be getting in the way.
There are also some errors mentioned:
An uninstall and Run-As-Administrator reinstall of Virtualbox may be needed. Try Virtualbox after this and see what happens.Not signed with the build certificate
If the reinstall does not fix the problem, please uninstall (not disable) Kaspersky and all other "security" software, and let Windows Defender run. Try Virtualbox, and see what happens.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Virtual Box stopped running virtual drives
The VBoxHardening.log file with the name win3.1-2022-12-09-10-52-00.log indicates VirtualBox 6.1.14. The certificate signature error means that VBoxDrv.sys or VBoxSup.sys has a different version than VirtualBoxVM.exe (the driver name and the certificates both were changed in the course of different VirtualBox 6.1.x updates).
Re: Virtual Box stopped running virtual drives
Ok, Turning off Kaspersky, uninstalling VirtualBox, rebooting, re-installing as administrator, and running it seems to be working.
Ok - these are working:
Puppy Linux
Win3.1
Win98se
WinXPx32
That's it! Thanks! It WAS Kaspersky that was causing the problem. Disabled it. Haven't decided if I want to take it out completely or not yet.
But thanks again! You guys are super-duper!
Ok - these are working:
Puppy Linux
Win3.1
Win98se
WinXPx32
That's it! Thanks! It WAS Kaspersky that was causing the problem. Disabled it. Haven't decided if I want to take it out completely or not yet.
But thanks again! You guys are super-duper!