Every Windows Guest install results in a corrupted OS

[Cypher]

Recently all my Windows 7 VMs have been getting corrupted and unusable, and any other installation becomes corrupted and unusable, too.

Common errors I get: 0x80070570, 0xc000007b, "The recycle bin on C:\ drive is corrupted. do you want to empty the Recycle bin for this drive."

Worst part is these are just on fresh installs and I haven't done anything to them yet. So I was wondering if this is a VirtualBox thing, my drive dying, or my iso is corrupted?

First, I don't think its my drive since it works fine outside of the VMs as I use it for extra storage as well. Also, my drive doesn't make any clicking noises and I disabled windows from putting it to sleep so it doesn't constantly spin up and wear out
Second, the iso I use to install Windows is one I've used multiple times on multiple PCs and have never experienced corruption.

The last thing I did before all these issues started popping up was updating Virtualbox to 5.0.28 after receiving the notification and later using CCleaner in one of the VMs (I suspect CCleaner but I don't think it would affect the host?).

Host OS:
Windows 8.1 Professional x64
i7-2600 (4 core w/ hyperthreading)
16GB Ram

Guest OS:
Windows 7 Home Basic x64 (Originally Ultimate, but the corruption made it unusable, was able to retrieve my data though)
2 Cores from Host OS
4GB Ram

This is nothing unusual as I've used this setup for 6+ months now and everything has worked fine.

I feel its dumb to assume its VB causing the issue, but I also ran a CHKDSK on the HDD containing the VM and its snapshots (.sav) had some issues with other files where "both own logical clusters".

Any ideas? Thanks!

[mpack]

What were the results of your host and guest filesystem checks?

[socratis]

Since this issue has not been widely reported (in fact it's just you) and since Win7 is one of the most used guests, I would tend to think that it's either your host or the ISO.

Recently all my Windows 7 VMs have been getting corrupted and unusable

All? How many are we talking about here? And all of them are exhibiting the same symptoms?

my drive doesn't make any clicking noises

That's not a necessary indicator. If it does click, it is a sufficient indicator.

I disabled windows from putting it to sleep so it doesn't constantly spin up and wear out

I'm sorry, but you have that backwards. If you don't put it to sleep, it does spin all the time.

had some issues with other files where "both own logical clusters".

Could you expand on that one? That doesn't sound like "no problem". At all...

[Cypher]

Since this issue has not been widely reported (in fact it's just you) and since Win7 is one of the most used guests, I would tend to think that it's either your host or the ISO.

Ah my bad, I should have clarified. I had 1 Win7 VM that I've used for months, when this issue started I created other VMs to see if I can replicate the issue where it would randomly start file checking (CHKDSK) and generating errors. Unfortunately, this is happening with all of them. Sometimes I get lucky and can get through a clean install, however as soon as I restart or shutdown then start the VM again, the issues arise.

Could you expand on that one? That doesn't sound like "no problem". At all...

I don't think I said its no problem but this is just 1 line out of the chkdsk on the HDD with the guest.

Code: Select all

File "\VirtualBox VMs\Home Basic\Home Basic.vdi <0x10,0x1ca3a>" and file "\Test\Screenshots\Thumbs.db <0x5,0x20634>" both own logical clusters [0x2ee5266, 0x2ee5da8)
        ... queued for offline repair.

What were the results of your host and guest filesystem checks?

No issues from host,
and the guest host gives me
sfc /scannow: corrupt files have been found and can't be fixed
chkdsk: A huge amount of recovering orphaned files, fixing indexes, I wish I can get the log but the VM won't load lol.

[socratis]

both own logical clusters

No issues from host

That looks like a problem in the host if you ask me. And I don't necessarily mean the HD that the host is booting from, that's not the only host attached HD. The HD that you store your VMs is having trouble. That may reflect on the guest HD. Which pretty much is a file on your host, and not only that, it is referenced by name as having errors!

sfc /scannow: corrupt files have been found and can't be fixed
chkdsk: A huge amount of recovering orphaned files, fixing indexes

You have some serious problems. First of all, sfc scans for "mismatching"/corrupt files, in the sense that they are not the original files, or the files that are supposed to be in the system. Usually this happens if you install applications that alter system files. That's what SFC stands for; System File Checker. It checks files, not the integrity of the HD. That's a problem with the OS, not with the disk.

I wish I can get the log but the VM won't load

So, we're talking about a host that has a problem with its disk, which results in a VM that won't load. Which makes perfect sense.

One question only; since you can't load the VM, how on earth were you able to run "sfc" and "chkdsk" on the VM?

[Cypher]

That looks like a problem in the host if you ask me. And I don't necessarily mean the HD that the host is booting from, that's not the only host attached HD. The HD that you store your VMs is having trouble. That may reflect on the guest HD. Which pretty much is a file on your host, and not only that, it is referenced by name as having errors!

You have some serious problems. First of all, sfc scans for "mismatching"/corrupt files, in the sense that they are not the original files, or the files that are supposed to be in the system. Usually this happens if you install applications that alter system files. That's what SFC stands for; System File Checker. It checks files, not the integrity of the HD. That's a problem with the OS, not with the disk.

I'll switch out the HDD thats holding the hosts with another one I have laying around and test it. Also thats weird that SFC is giving me that issue because I never install anything that edits system files (unless CCleaner is one, but even then it shouldn't affect the host?) or touch system files at all, but I'm guessing the fact that the OS is messing up that stuff gets altered?

So, we're talking about a host that has a problem with its disk, which results in a VM that won't load. Which makes perfect sense.

One question only; since you can't load the VM, how on earth were you able to run "sfc" and "chkdsk" on the VM?

Sometimes the installation of the OSs can last longer than others before I can't even run them anymore because they wont load at all. Like even if I restart the VM it does the CHKDSK and will sometimes pass through and let me continue onto windows. As a result, I can then run sfc.

Sorry I dont know the right wording for it but its that where some VMs can 'last longer' than other ones before they stop loading.

[socratis]

I'll switch out the HDD thats holding the hosts with another one

OK, we'll need to get the terminology right:

• HOST: your computer that you boot into.
• GUESTS: the virtual machines that run on top of the host.

They are distinct and have no interference with each other. Let's get that clear. So, you can't have "hosts". Period.

So, with that in mind, please keep the descriptions as clear as possible. Don't say "I run SFC and...", say "I run SFC on the host and...", just so that we're on the same page.

If you've never installed anything in the guest then something is wrong with your ISO. Is it an official one? Name and md5sum please.