Page 1 of 1
Windows Guest Additions always reboots
Posted: 4. Apr 2012, 20:55
by markus5
When I install the guest additions with the /S option (silent), a reboot is always done. I need to prevent the immediate reboot. Ideas?
Regards.
Re: Windows Guest Additions always reboots
Posted: 4. Apr 2012, 21:10
by Perryg
Try it without the /s option
Re: Windows Guest Additions always reboots
Posted: 4. Apr 2012, 22:01
by markus5
Without the /S its interactive, and doesn't reboot unless you check 'reboot now'. But, I want unattended installation.
Re: Windows Guest Additions always reboots
Posted: 5. Apr 2012, 09:27
by squall leonhart
markus5 wrote:Without the /S its interactive, and doesn't reboot unless you check 'reboot now'. But, I want unattended installation.
Sucks to be you.
Re: Windows Guest Additions always reboots
Posted: 5. Apr 2012, 16:27
by markus5
squall leonhart wrote:markus5 wrote:Without the /S its interactive, and doesn't reboot unless you check 'reboot now'. But, I want unattended installation.
Sucks to be you.
Yes, sometimes it does. It would suck less if someone proposed a solution.
Re: Windows Guest Additions always reboots
Posted: 5. Apr 2012, 16:39
by Perryg
I did provide a solution. Don't use the /s option. The reason why it has to reboot is because the drivers don't take effect until after the reboot so installing silent and not rebooting will simply not do anything.
Re: Windows Guest Additions always reboots
Posted: 5. Apr 2012, 17:45
by markus5
Perryg wrote:I did provide a solution. Don't use the /s option. The reason why it has to reboot is because the drivers don't take effect until after the reboot so installing silent and not rebooting will simply not do anything.
You are correct.
I'll be clearer. I want unattended installation without a reboot. I will reboot later.
Can that be done? Looking at the code, no. But, I might be missing something.
Thanks.
Re: Windows Guest Additions always reboots
Posted: 5. Apr 2012, 18:03
by Perryg
Yes there is a way but not suggested as it can cause bad things to happen. When you install a package that changes drivers it removes them and replaces then with the new version. So if you continue to use the old drivers (that are locked) all new calls will try to use the new drivers. Weird of not dangerous things can happen.
This really is not a VirtualBox issue either but a Windows installer issue, if you want to call it an issue. I prefer to call it the proper way.
You can find the switches to usurp the reboot by typing windows silent install without reboot in your favourite search engine, but no complaints here if you proceed with this approach.