3d DriveGuard After Win10 Creator Upgrade Error

[KellyCraven]

3d DriveGuard causes and error after each rebood since the Win10 Creator Edition Upgrade.

AcceleratorST hits the error as is says VSRealtime140.dll is missing....reinstall the app...

All previous suggestions seem to not apply, don't work, etc.

What I've done, per all suggestions from both the HP forum and Microsoft community?

Install the 2010 VS Runtime Package for both 32 and 64 bits. There were links to these on both HP and MS forums. This was a fix from months ago when Win10 initially screwed up 3d DriveGuard. This fix no longer works, maybe because neither the 32 nor 64 bit packages will sucessfully install on Creator Edition. The install fails because newer versions of the DLLs are detected - set up stop with a prompt to fix the conflict. Not sure how to fix this situation except to rollback the Creator Update.

Searched and downloaded the 3d DriveGuard app for my specific machine. It matches the previous one installed. No other versions are found for my machine.

Ran the 3d DriveGuard set up and selected Repair.  This didn't change anything, though it may or may not have succeeded. The setup just ended. There was line in the resulting log that a reboot was needed. After a reboot the error was back.

Uninstalled 3d DriveGuard.  Rebooted and there was no error. This confirms the error is indeed from 3d DriveGuard.

Install 3d DriveGuard again.  The setup may or may not have succeeded. there was no "finished" notification. The setup just ended. The log shows that a reboot is needed to continue. Rebooted.  The error is back, just like before.

Even though the erroe is caused by a Windows Update Microsoft is passing the buck back to HP. They are no help.

Since there is no compatible 3d DriveGuard for my machine is my only option to uninstall and leave it uninstalled?

Does 3d DriveGuard give protection we need? (I'd say yes)

What do you suggest as my next step? (there are MANY people having this issue based on the comments seen)

Thanks

[Paul_Tikkanen · Accepted solution]

Hi:

See if this works...

Open the Windows Control Panel, select Programs and Features, right click the entry for the HP 3D DriveGuard, and select Uninstall.

When this has completed, restart the notebook.

When you are at the Windows desktop, download and install this version of HP 3D DriveGuard at the link below, and restart the PC.

http://ftp.hp.com/pub/softpaq/sp78001-78500/sp78033.exe

[KellyCraven]

EXCELLENT!!!  This worked perfectly.  Thank you very much for the surprisingly fast response.

The version of 3d DriveGuard link to in the fix was not available as an option for my machine. How could I have searched and found this for my machine?

There also didn't seem to be a way to poke in that my machine was running Win10 Creator, so I assume the only apps, utilities, and drivers offered for my device are for it in it's clean from the factory state (Win8.1).  By not making it easy (even stupidly easy) to find alternate apps, utilities, and drivers, many of us that have upgraded the OS end up being stuck and have to resuly to public posts or learn to "live with issues", and of course that makes the experience not too good.

There was no offereing of an updated 3d DriveGuard via HP Support Assistant either.  This is the most logical place this should have been found.

There are SO many different "fixes" for this that don't apply anymore I hope everyone that sees this thread will have the experience I did.

Thanks again, Paul. 

[Paul_Tikkanen]

You're very welcome.

Yes, unfortunately with what seems to be semi-annual major updates to W10, we are left to our own devices to help each other out, by coming up with creative ways to fix odd-ball issues.

HP does not do a good job keeping up with these changes and driver updates are few and far between.

On older models, these updates do not get posted to the driver pages.

Here is the list of notebooks covered by the driver I posted.  Cryptic at best...

ftp://ftp.hp.com/pub/softpaq/sp78001-78500/sp78033.html

I think as W10 evolves, more and more of us will fall by the wayside, and will have no choice but to stay with the version of W10 that last worked for us without issues.

For example, the Creator update wiped out every one of my PC's audio drivers, and I had 3 different drivers to contend with...IDT, Realtek and the ADI Soundmax.

I was lucky this time in that I was able to use the W8.1 IDT audio driver to fix my HP notebook, the W10 realtek audio driver directly from Realtek to fix 2 of my HP desktop PC's and was able to use the W7 Soundmax driver to fix my 3rd HP desktop PC.

I fear that eventually, I will not be successful in finding a workaround, if this happens again.

[KellyCraven]

I wish there was some way to plan for this stuff there really isn't.

What I don't understand about Creator is what it changed in the OS that caused so many little issues in places it shouldn't based on what we were lead to believe was in the upgrade.

I have three laptops and a desktop. All laptops are HP and the desktop is self put together. The oldest laptop has Win7 and is sort of still hanging in there, though barely. (it has a regkey installed to prevent upgrade to Win10)  The desktop is patiently waiting for the Creator Upgrade to trickle in. (any day now I'm sure). The other two laptops....well...

I bought one of these (the one in question for the problem in this thread) as a replacement for the old Win7 laptop. Even though it was an nearly exact replacement spec-wise and had double the RAM the new one was WAY underpowered, ran hot and slow, and lacked a bay for a second hard drive (didn't know until I got it). I couldn't use it as a replacement.  I was very disappointed. I even had to set the max CPU to about 80% to keep the fan from screaming full speed at all times after it was upgraded to Win10 from Win8.1.

Because I couldn't use the first replacement I picked up a higher end HP from the same vendor. 16G RAM, 2T hard drive, 17" screen like the others, i7 Intel.  I was very happy with that one.  I want another....don't make this config anymore...sorry I digress.

So, Win10 Creator comes in a couple of weeks ago on  the fast good laptop. There are major issues (including the 3d DriveGuard problem).  The MAJOR problem is that it will no longer wake from sleep or hibernation, and is slow to boot, when it boots. This change was immediate after the upgrade. It would semi-hang when coming out of sleep/hibernation. The only way to get booted was to turn it off and cold boot, then it was fine, until the next day.

Turning off that machine was not good...turn off being loosely used. I had to pull the power supply and yank the battery. This was hell on the hard drive and caused errors. (ChkDsk abd  SFP) Had to reinstall some apps to get them to run. Eventually, the hard drive died. Shipped it back to HP on Friday. When I get it back it will have Win8.1 and the whole upgrade to Win10 fiasco will start new, as will trying to get all my apps reinstalled.  (apps and data were backed up a few weeks ago so not too much was lost). 

BUT!!! Why I am I mentioning this?  I do audio, multitrack recording, etc, and the idea that Creator nuked the audio drivers on somone's multiple machines is VERY troubling to me. I'm already POed at Microsoft (for a lot of reasons that I can go on and on about...I was an audio test dev for almost 20 years) but if the pending update kills audio on the desktop I'll be even more POed...and with more reason to be bitter.  (grin)

I'm appalled that MS is using telemetry in place of more viable testing before pushing these updates. We're all beta testers now, and most people aren't savvy or knowledgeable enough to be able to fix things when these updates do go well. Most folks are screwed.

[Paul_Tikkanen]

For the sleep and wake issues, did you install the very latest Intel Management Engine Interface driver?

My understanding is that might be the cause of that problem.

I would need to know the full model number or product number of your notebook in order to provide that driver.

The product number can be found on the same sticker as the serial number.

[KellyCraven]

Hadn't given any thought to needing to update those things. I've assued the HP Support app would let me know, or do it for me.

Point is moot on the machine going back to HP of course.

ID for this laptop:  E8B97UA#ABA

I pick these up at Costo - convenient and good price, and having the extended warranty at no extra cost is a plus, especially these days.

Thanks for the help. 

[Paul_Tikkanen]

Hi:

The specs state that it has an AMD processor and chipset. 

I thought I had read in your reply that your notebook that had the sleep issues had an Intel i7 processor.

The IMEI driver is only applicable to newer PC's with the Intel processors and chipsets.

Now, if it is the above model that is has the sleep issues, I don't know if you would want to try it or not, but there is an AMD chipset driver you could install directly from the AMD website.

First driver on the list.  Install and restart the PC.

http://support.amd.com/en-us/download/chipset?os=Windows%2010%20-%2064

[KellyCraven]

You read right.  I didn't think about "this" laptop being AMD (this one with disappointing perf...perhaps being AMD is the issue there...I don't usually get AMD...and that's even though I said it was close to the same specs as the machine it was to replace, not being Intel was another difference, and that's not a minor difference).

The i7 laptop did have those issues. That's the laptop on the way back to HP for "fixing" because the hard drive failed.

THIS laptop, the AMD, does have a minor wake issue, but it's not related to the hard drive I don't think. It comes up with a black screen and no visible mouse pointer sometimes. The fix, so far, is to close the lid and reopen it 30 seconds or more later. This issue was more common in the online comments when the winupdate previous to the Creator update came out. That update hit my machines on 5/23 or so. Yes, the i7 machine did have minor black screen issues after that update, but this AMD did not.

Sorry for the confusion. It's my fault for overly expanding this thread into multiple machines and possibly unrelated issues to the original post. 

At the moment this AMD is doing fine. I'll check out the updates, and bookmark the links. They will be handy, especially when the i7 machine gets back.

THANKS!!!

[Paul_Tikkanen]

The only suggestion I can offer otherwise would be to uncheck the fast startup option in the power options menu.

I have an old HP business notebook from 2007 that actually runs W10 CE just fine as long as I disable the fast startup.

Intel processor, AMD graphics.

If it is enabled, I only get a black screen after the HP splash screen goes away, and Windows loads the graphics drivers.

With fast startup unchecked, it works perfectly fine.

Go figure.