Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • You have rolled back to the previous version to determine if this is connected to something that has changed with the program or something else entirely?
    – Ramhound
    Commented Nov 5, 2015 at 17:12
  • While I discovered the behavior change during an upgrade of VirtualBox, I don't suspect it's really related to VB. But, to make certain, I took your suggestion and rolled back to the previous version of VB. As I suspected, the changed behavior still exists. I suspect it's most likely due to a Windows update. This is a company machine that is set up to automatically apply any and all Windows updates.
    – Captain
    Commented Nov 5, 2015 at 17:35