virtualbox.org

Yesterday, i had a problem with VirtualBox 6.0.14 after installing Windows 10 Update package KB4549951...

After installing it and restart, i started my VMs... both of them almost at the same time, i didn't wait for the 2nd for a few secs. Then, the starting process of the 2nd was suddenly frozen: "VM is starting", until this morning. So i waited for more than 12h and the start was not successful.

!!!! I NEVER HAD THAT BEFORE INSTALLING THAT UPDATE !!!

Then i disabled "Data Execution Prevention" completely, and now i didn't have problems anymore.

Maybe someone has / had similar problems like me?

the "dumb" windows 10 users do provide the test environment for later M$ server OS updates. that's a fact.

f**k m$!!!

Can you repeat the exact same process and have the exact same results? If you uninstall the update, does the the exact same process have the exact same results?

No proof for that, and no time to proof. I'm sorry...

"No proof for that, and no time to proof. I'm sorry..."

On the "other side": I never had that beahvior before, never ever... so there seems to be a relation with that update. (maybe in combination with my hardware?) I don't know to disable DEP is a fix, but i tried it at lease and now it works. But maybe it occurs again..? If yes i will post that too...

Disabling DEP (Data Execution Prevention) seems like wild use of the internet without having AV installed, perhaps. I wouldn't leave things like that myself.

jmar83_the2nd wrote:no time to proof.

If that means you don't want to try to uninstall the update and see if the issue goes away, the I guess that's that. But so far (and yes there always has to be a first report) but yours is the only report, so maybe something else is wrong besides that update? Just sayin'...

And if you have the time to report this but haven't the time to start two guests really quick on each other to see if the problem repeats, then we really are done.

FWIW I have 6.0.14 on a 10 host and KB4549951, started two guests one slam after the other, and no trouble.

Without further input, we have FUD here, move along citizens...

It's more "i can't" than "i don't want", because it's a productive system. And i don't have the time to build up the same config on another machine. And regarding to the hardware: No, i will not buy a 2nd server for 1000s of $ just for that (NOT mea culpa...), hehe! ;-)

"FWIW I have 6.0.14 on a 10 host and KB4549951, started two guests one slam after the other, and no trouble."

That kind of problem may be impossible to reproduce - so no chances to be realistic! :-(

Yeah, I can see that editing a production machine would be hard to do. If it never happens again I'd write it off as a one-time glitch. It's Windows, glitches happen...

Yeah, that's all too complicated. I'm sorry... i only hope the problem never occurs again, that's all.