DKW3
Contributor
Hi,
When I recently downloaded a new version of DriverMax, it had an issue related to not finding a component of Microsoft Visual Studio 6.0 which was strange, because I had NEVER installed VS6.0 on my Windows 7 installation.
But simply to be rid of this annoying "event ID error", I went ahead and attempted an install of the VS6.0 software, initially via an online tutorial that advised some preparatory installations, such as "VB common controls", and the "MsJava.dll" registration. However, no luck.
So after manually removing the previous preparatory installations to the best of my ability, I tried installing VS6.0 using the "vbcorner.net" installer software, of which the installation was a success.
But I guess I didn't catch every, single element of the previous "VB Common Controls" removal, because now there is a corrupted component that nether using SFC / Scannow when booted, SFC / Scannow from the Win. 7 Disc using the "offbootwindir..." in CMD, or the basic SFCfix scan (with the Win. 7 Disc in the drive as requested), can fix.
I have uploaded my most recent CBS.txt with the copied sfc.fix text pasted below the line, and I hope this can be figured out, as I'm not 100% sure if it is even related to VB6.0, which is why I wrote "Possibly Related" in the Thread title.
But I know for certain that I had no "corruption" issue that SFC /Scannow couldn't address just one week prior, when I ran it just for maintenance ("Update Agent" being the usual culprit). Thanks.
-DKW3
When I recently downloaded a new version of DriverMax, it had an issue related to not finding a component of Microsoft Visual Studio 6.0 which was strange, because I had NEVER installed VS6.0 on my Windows 7 installation.
But simply to be rid of this annoying "event ID error", I went ahead and attempted an install of the VS6.0 software, initially via an online tutorial that advised some preparatory installations, such as "VB common controls", and the "MsJava.dll" registration. However, no luck.
So after manually removing the previous preparatory installations to the best of my ability, I tried installing VS6.0 using the "vbcorner.net" installer software, of which the installation was a success.
But I guess I didn't catch every, single element of the previous "VB Common Controls" removal, because now there is a corrupted component that nether using SFC / Scannow when booted, SFC / Scannow from the Win. 7 Disc using the "offbootwindir..." in CMD, or the basic SFCfix scan (with the Win. 7 Disc in the drive as requested), can fix.
I have uploaded my most recent CBS.txt with the copied sfc.fix text pasted below the line, and I hope this can be figured out, as I'm not 100% sure if it is even related to VB6.0, which is why I wrote "Possibly Related" in the Thread title.
But I know for certain that I had no "corruption" issue that SFC /Scannow couldn't address just one week prior, when I ran it just for maintenance ("Update Agent" being the usual culprit). Thanks.
-DKW3