[BIG ISSUE] Could not open any VM on VirtualBox after win10 updated by 2017/11 !?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[BIG ISSUE] Could not open any VM on VirtualBox after win10 updated by 2017/11 !?

魏嘉宏
Hello, guys

1. Try to uninstall current version, and install old version >> not worked
2. Entry "regedit", change the OS machine key >> not worked
3. Do nothing, just recover to windows version from settings >> YAP!!! it worked.

Anyone else could tell me what happened to windows updated?
I hope Vagrant would follow VirtualBox version to upgrade.
But someone need to tell VirtualBox to fix this problem first.

Thanks for your time.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c2450e7b-5d88-4ff2-95c9-eca7d45b3cab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [BIG ISSUE] Could not open any VM on VirtualBox after win10 updated by 2017/11 !?

Alvaro Miranda Aguilera
Hello

Could you share more information.

Host OS?
VM Os?
Vagrant version?

What you did upgrade? host os?

What error you get?

Screenshots?

Thanks
Alvaro

On Wed, Nov 8, 2017 at 10:46 AM, 魏嘉宏 <[hidden email]> wrote:
Hello, guys

1. Try to uninstall current version, and install old version >> not worked
2. Entry "regedit", change the OS machine key >> not worked
3. Do nothing, just recover to windows version from settings >> YAP!!! it worked.

Anyone else could tell me what happened to windows updated?
I hope Vagrant would follow VirtualBox version to upgrade.
But someone need to tell VirtualBox to fix this problem first.

Thanks for your time.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c2450e7b-5d88-4ff2-95c9-eca7d45b3cab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exWUfGuoSbHUpkj5%3DjBt-O_CScbTBrpgQoWs51eUFpt2g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [BIG ISSUE] Could not open any VM on VirtualBox after win10 updated by 2017/11 !?

魏嘉宏
1. Host OS: win10
2. Guest OS: Linux Ubuntu
3. VirtualBox version: 5.1
4. Vagrant version: 1.9.4
5. Just Update the Win10.( u all know to be forced to upgrade, no matter u need or not!!)

My situation: 
1. upgrade you OS win10 version
2. you dont need to start up your vagrant at all
3. JUST start you VM or Create a new VM to start up, then be crashed. You will see the message, "E_FAIL (0x80004005) ...."
4. Just set you OS win10 to restore to previous version. Everything would be fine as usual.



2017-11-08 20:57 GMT+08:00 Alvaro Miranda Aguilera <[hidden email]>:
Hello

Could you share more information.

Host OS?
VM Os?
Vagrant version?

What you did upgrade? host os?

What error you get?

Screenshots?

Thanks
Alvaro

On Wed, Nov 8, 2017 at 10:46 AM, 魏嘉宏 <[hidden email]> wrote:
Hello, guys

1. Try to uninstall current version, and install old version >> not worked
2. Entry "regedit", change the OS machine key >> not worked
3. Do nothing, just recover to windows version from settings >> YAP!!! it worked.

Anyone else could tell me what happened to windows updated?
I hope Vagrant would follow VirtualBox version to upgrade.
But someone need to tell VirtualBox to fix this problem first.

Thanks for your time.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c2450e7b-5d88-4ff2-95c9-eca7d45b3cab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/DQxRRCmSrSU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exWUfGuoSbHUpkj5%3DjBt-O_CScbTBrpgQoWs51eUFpt2g%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.



--

魏嘉宏

E-mail : [hidden email]

Mobile: 0953691026

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CADsbm6-WcHTm3y7zbsOpZ8zBqQenrcW7T0_Vq%3DKo2AfhyKkrAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [BIG ISSUE] Could not open any VM on VirtualBox after win10 updated by 2017/11 !?

Alvaro Miranda Aguilera
after the upgrade, Can you reinstall Virtualbox? version 5.1.30  is good.

I have 3 machines on latest win10 version and Vagrant + virtualbox runs fine.

 "E_FAIL (0x80004005) ...."

is a Virtualbox error

if you can open Virtualbox GUI and try to create an start a VM? any error?

Please share screenshot.

Thanks
alvaro

On Thu, Nov 9, 2017 at 2:25 AM, 魏嘉宏 <[hidden email]> wrote:
1. Host OS: win10
2. Guest OS: Linux Ubuntu
3. VirtualBox version: 5.1
4. Vagrant version: 1.9.4
5. Just Update the Win10.( u all know to be forced to upgrade, no matter u need or not!!)

My situation: 
1. upgrade you OS win10 version
2. you dont need to start up your vagrant at all
3. JUST start you VM or Create a new VM to start up, then be crashed. You will see the message, "E_FAIL (0x80004005) ...."
4. Just set you OS win10 to restore to previous version. Everything would be fine as usual.



2017-11-08 20:57 GMT+08:00 Alvaro Miranda Aguilera <[hidden email]>:
Hello

Could you share more information.

Host OS?
VM Os?
Vagrant version?

What you did upgrade? host os?

What error you get?

Screenshots?

Thanks
Alvaro

On Wed, Nov 8, 2017 at 10:46 AM, 魏嘉宏 <[hidden email]> wrote:
Hello, guys

1. Try to uninstall current version, and install old version >> not worked
2. Entry "regedit", change the OS machine key >> not worked
3. Do nothing, just recover to windows version from settings >> YAP!!! it worked.

Anyone else could tell me what happened to windows updated?
I hope Vagrant would follow VirtualBox version to upgrade.
But someone need to tell VirtualBox to fix this problem first.

Thanks for your time.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c2450e7b-5d88-4ff2-95c9-eca7d45b3cab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/DQxRRCmSrSU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exWUfGuoSbHUpkj5%3DjBt-O_CScbTBrpgQoWs51eUFpt2g%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.



--

魏嘉宏

E-mail : [hidden email]

Mobile: 0953691026

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CADsbm6-WcHTm3y7zbsOpZ8zBqQenrcW7T0_Vq%3DKo2AfhyKkrAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewRCVD6eCJftHnc1z7xwtAr7i5tFqRs4oWSPpS2G7iyRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.