Recently when loading vt+ it said error 339, can't error with sysinfo.ocx or something similar. I tried registering it again and also replacing the ocx file then when looking on vt site it advised to download vt+ again and re-install.
On my client's computer that's worked (they had the same problem) but I hadn't meddled with the ocx file. Unfortunately on my computer re-installing hasn't helped, it says while installing that sysinfo.ocx can't be registered. I've tried it again using the command prompt but its saying the file can't be registered. Any suggestions?
__________________
John
Any advice given is for general guidance and professional advice should be sought applicable to your circumstances.
Always a good idea to mention what version of Windows you are running when this sort of situation occurs in case the issue is a recent update nobbling the file - especially if it's Windows 10, for which ordinary users are now effectively beta testers for Microsoft, and updates causing problems isn't entirely uncommon. Also what A/V software you are using.
A quick search online and no recent update problems are jumping out at me - though one A/V one is: MSE was flagging that file as being infected with a worm at the end of March, but was fixed within a couple of days.
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
Its windows 10, my VT+ at home is working fine, that's also W10, although I very rarely access VT+ on that machine, so it may be that whatever was wrong with sysinfo at beginning of April was fixed before I accessed my machine at home.
The error on my office machine would have occurred around that time, and I replaced my sysinfo file on my machine with one downloaded from the net. This is the one that VT+ install can't get past. It won't let me register the file via the command prompt (administrator)
No other programs seem to be affected.
__________________
John
Any advice given is for general guidance and professional advice should be sought applicable to your circumstances.
Just because it's working on your Windows 10 machine at home, don't let that to fool you into thinking it's definitely not a Windows 10 problem - as well as them (probably) being different hardware with different drivers, which may affect (or be affected by) the OS differently, etc, you'll also find the updates don't necessarily hit them at the same time. Microsoft rolls updates out gradually, so not all computers get them at the same time.
By the same token, that doesn't mean it IS a Windows 10 problem. However, my gut instinct now when someone reports a problem with something on a Windows 10 computer is that Windows 10 is the problem - this has proven to be the case more often than not with computers I've looked at. Unfortunately, because I've been successful - so far - in my avoidance of that OS on my own kit, it also means that unless the pile of poo is on the desk in front of me so I can tinker and work out where things are, my abilities to suggest fixes are limited!
That said #1, you mention the beginning of April which I'm equating to the end of March in what I said. That was in reference to MSE - Microsoft Security Essentials - rather than Win10 itself. Do you run that? If so, and if it's possible that caused the problem, you should find the file in whatever system it uses to quarantine files, and if it's there you should be able to tell it to restore.
That said #2, my standard suggestion might help - if Windows 10 allows you to do this. Whenever something mysteriously stops working or whatever, I usually suggest looking at the restore points to find the last one before the problem started - and restore it. If there's been a long gap between the program working and the next time it was used/when it was b0rked, there may be multiple points: Use the latest one and work backwards.
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
Ah bugger, I never told you the A/V. It was Mcafee but I deleted it on Friday cos it had run out and put AVG on instead. I had toyed with doing a system restore but didn't really want to go back to March. That said I don't think I've installed anything major this month so I'l have a look at doing that on Tuesday, when I'm next in the office. I'll let you know how it goes. Thanks a lot Vince, much appreciated.
__________________
John
Any advice given is for general guidance and professional advice should be sought applicable to your circumstances.
I went to do a system restore, but it only took me back to 19th April. I had the option of doing a system reset, but that would have meant re-installing all my programs again. Then I had a brainwave, I deleted the file and then tried to re-install VT +, bingo, it re-installed.
__________________
John
Any advice given is for general guidance and professional advice should be sought applicable to your circumstances.
Ha! Yes - that does actually make some sense. VT presumably includes the file as part of its installer, so the existing problem file was causing problems with the installation; simply getting rid of it allowed the installation to proceed.
Sometimes the obvious answer isn't all that obvious, except with hindsight.
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
