[Solved] VirtualBox won't install after NTLite upgrade (Win7)

P

pmikep

Active Member
Does anyone have any ideas about what components are needed for VirtualBox to install? Powershell?

Good news/bad news. The good news is that I found my "Flag 9" problem. (I had let NTLite trim too much from my image. I went back and kept the .win 2 (Setup). So then I was able to upgrade my old Win7 with a fresh reinstall of Win7 + NTLite.

Most of my apps are working as they used to. (I had to fight Comodo, for reasons below.)

Now the bad news. My old Win7 had VirtualBox working. My updated version does not. Nor can I install VirtualBox now. It get's about to the point where it wants to install the Network Adapter and then rolls back. saying that the Install failed.

Maybe some of this is my fault, because in the new NTLite'd Win7, I changed a few of the network things. For example, I removed SMBv1, which removed some low level networking stuff, like NetBUI.

So, either because of that, or just because Windows starts over when you upgrade, some things had changed in the Properties Box for my NIC. For example, the Comodo virtual firewall thing was gone. (So I had to use a cleanup utility to remove Comodo.)

Since I had NetBIOS in the old VirtualBox Virtual Host adapter, I presume that is why the VBox adapter is gone now.

Anyway, it appears that I have removed something from Win7 using NTLite that prevents VirutalBox from installing. Looking for ideas. (I updated Trust Certificates. That didn't fix it.)
 
Last edited:
pmikep said:
Wow squared! WinMerge is fantastic. I especially like the "Copy to the right" feature.
Click to expand...
Maybe Beyond Compare has more features, you can select separated lines with Ctrl key + mouse and then copy all of them or select a section and unselect one or more lines that you won't move.

pmikep said:
Yeah, I should probably try the beta. But I'm trying to be like you now and take it one step at a time.

If I were smart enough, I could converge from two different directions.
Click to expand...
Patience is the key.

You can run stable version for removals and beta for read and display what you have removed earlier. I prefer xml file comparisons.
 
You also need time and be totally obsessed with liting, along with a constant supply of tea, nicotine and a barracks knowledge of profanities. nLiting xp also helped.
 
Solved. (I'll try to change the title of this post if I can.)

Here was the problem: <Tweak name="AuthRoot\DisableRootAutoUpdate">1</Tweak>

(In English, "Automatic Update of the Root Certificate Trust List." (Under Settings.)

It needs to be left at Default. (I had set it to Disable.)

I had set Windows Update to "Never update" - and had also set the Update Service to Manaul. So I had figured "Might as well prevent WSUS from updating Root Certificates too" just to be sure Microsoft (or the US Govt) does sneak something in.

But apparently, Virtual Box needs to update the trusted Certificate when it installs its virtual NIC adapter.

I should have been able to figure this out in advance, because, in the VBox Forums, one of the fixes for the problem I was having was to download a Root Cert update file and manually import that into Windows.

I had tried that. But because I had disabled Windows from updating the Root Cert, even this manual import failed, sending me off on a wild goose chase.

(In my defense, I thought that this "Automatic Update of the Root Certificate Trust List" only applied to updates from Windows Update Service. Also, in its GUI, WSUS Offline offers a check box to update Root Certs from Microsoft's wsus. So again, I thought this setting only applied to Windows Update.)

In retrospect, I should have been able to home in on this problem sooner - if I had Clanger's discipline. It took 20 iterations, at about 35 minutes each (about a day and a half) before I found the problem.
 
Last edited:
You bug hunted(game over man) using the same, erm, err, you wernt gonna let this bastard beat you. Nice one :) :cool:
 
Many programs install their Trust certificates (driver and secure conection related).

To be safe, i don't change Windows services other than search, themes, desktop window manager and Windows Update and in extra services, Beep something.
 
Yeah, I should be more conservative in my tweaking. I try to use Black Viper's recommendations for Services.
 
pmikep said:
I try to use Black Viper's recommendations for Services.
Click to expand...
I wanted to do the same but after reading dependencies in some services, stopped reading and only tweaked what i know is safe (based on what i wanted). Most of the times is not necessary because the removed components takes away those services.
 
That's a good point. I think there are only 50 20 Services running on my machine after NTLite.
 
Last edited:
So, since we're now talking about what System Settings should be preserved, I wonder if nuhi can lock out users from changing Settings like Root Cert Trust List when Recommended is enabled in Compatibility?
 
This tweak is being reported too many times as the cause of some weird issues, thinking of ditching it, everyone agrees?

Thanks pmikep.
 
You must log in or register to reply here.
Back
Top