#BOOTCHAMP TUTORIAL WINDOWS 10 INSTALL#
#BOOTCHAMP TUTORIAL WINDOWS 10 UPDATE#
#BOOTCHAMP TUTORIAL WINDOWS 10 PRO#
#BOOTCHAMP TUTORIAL WINDOWS 10 BLUETOOTH#
#BOOTCHAMP TUTORIAL WINDOWS 10 WINDOWS#

Since my error/crash was so reproducible, I thought it was happening for everyone. Yes, as my post above states, I have repeatedly removed/re-installed the Guest-Additions as 'cleanly' as I know how to.

#BOOTCHAMP TUTORIAL WINDOWS 10 UPDATE#

including Windows-Updates, Apple Software Update for Windows, macOS Updates, and VirtualBox for macOS.

#BOOTCHAMP TUTORIAL WINDOWS 10 INSTALL#

I didn't know we weren't suppose to install updates (to facilitate running the latest versions of all software). I didn't know it was deemed finicky, or that it's 100% functionality was a low-priority. I am aware that occasionally using VirtualBox v5.2.x to access my BootCamp-ed Windows-10/64bit install (as macOS-Guest via RawDisk) is rare, but I thought it was fully-supported. It seems I made some incorrect assumptions. If I have stumbled upon some kind of bug, how do we let the developers know so they can take a look and fix it if need be?įirst of all, thank you for the thorough answers. it seems that VBoxMouse.sys is indeed a mandatory part of GAs, and natively-booted Windows-10/64bit just doesn't like it being installed.

#BOOTCHAMP TUTORIAL WINDOWS 10 WINDOWS#

However, VirtualBox and Windows is now so many versions newer (not sure how that works with bug-reporting). Yes, installing a major-update (like from v1703 to v1803) is a good example of when a native boot of Windows works much better/faster.Ĥ. I can't re-install them because I regularly need to boot Windows-10 natively. Yes, this is what I am forced to do (run with no GAs). Thanks for confirming my current work-around is best available at the moment. I uninstalled the new v5.2.18 GAs, and everything is working fine again.ģ. same VBoxMouse.sys crash/error on native start-up/boot. Unfortunately, I still have the same problem. I then installed the matching-version GAs inside Windows-10 I saw that a new VirtualBox v5.2.18 was just relased, so I downloaded it, installed it, and upgraded my Ext-Pack. so it still booted and worked both ways (natively booted and inside VirtualBox). I upgraded my Windows-10 to current v1803 and installed all other available Windows Updates (much faster from a native boot). My previous attempt was on Windows-10 64bit v1703.

For example, I do not get the capture-prompt (like when Mouse Integration is purposely turned off).Ģ. Maybe there should be? I say that because while GAs are NOT installed, the mouse seems to working fine in VirtualBox (in macOS, running in a window).

#BOOTCHAMP TUTORIAL WINDOWS 10 BLUETOOTH#

The iHome mouse is also Bluetooth (v3.0).ġ. It's a Mac-Mini(Late-2012) with an Apple Bluetooth Keyboard. If it can't just work like before, is there some way to keep VBoxMouse.sys from being installed?Īt least, it would be nice to be able to use the other GA features. I really like using the Guest Additions when running my Windows-10 from Virtual-Box.

It seemed to be since it cleared-up after I uninstalled the new GA's. Not sure what was going-on with this Activation glitch, but thought I would mention it in case it was relevant. After I fixed it and got back into my Windows-10 (natively) I noticed it is Activated again (without any intervention on my part). Oddly, while it was broken, I noticed that my Windows-10 wasn't Activated any more (where previously, it always has been). The only fix that worked for me was to completely uninstall the new GA's from Windows-10. The only way into my Windows-10 install was through Virtual-Box (that way still worked fine). The computer has rebooted from a BugCheck. Windows Reliability Report says 'Windows Stopped Working. I searched Google and this forum, and tried a few things, but could never get VBoxMouse.sys to not crash on boot or to just not load any more. Even in this broken state, I could still continue to get into my Windows-10 install from macOS Virtual-Box reliably. I could never get past it and eventually, Windows-10 booted to a Startup Repair screen. However, when I tried to run Windows-10 natively (from Mac-Mini Option-key-boot), I got a VBoxMouse.sys crash near the Windows Login-Screen and Windows was showing this weird BSoD-like error-reporting screen. I installed the new version in High-Sierra along with the Extension-Pack (and then upgraded the new Guest-Additions inside Windows-10).Īfterwards, when running my Windows-10 from VirtualBox, it was still working pretty good. This was all working fine before I upgraded my VirtualBox from v5.1.x to v5.2.16. I use VirtualBox to run that same Windows-10 installation as a Guest from my macOS Host, but sometimes I need to boot Windows-10 natively.

#BOOTCHAMP TUTORIAL WINDOWS 10 PRO#

I have a Mac-Mini with High-Sierra v10.13.6 that is BootCamped with Windows-10 Pro 64bit.

Bootchamp tutorial windows 10