Some solutions require messing around with registry entries set by group policy, and I'm not sure I'm supposed to mess around with that. I would need IT to do that, and their response time is currently in the months right now. The closest thing still seems accessible is HP Client Security, but it requires a "Microsoft password". In the past, some have found it insufficient to disable it/them it/they had to be removed.Īll that I've found online about disabling them seem to be dated, as I do not see what is described, e.g., HP Sure Click on the System Tray (I may have disabled it in the past without recalling that now, but I still see its effects when downloading PDFs and Word documents). I might as well add that I've come across many accounts of incompatibility between VirtualBox and HP's built-in security on Elitebooks, with HP Sure Click being a major source of interference. I am working through Mpack's suggestions now. I find this (just a tiny bit) surprising, as my web wanderings revealed some speculation that Hyper-V might be used by HP Sure Click to open downloaded apps in "micro-VMs". Furthermore, the "Startup Type" shows "Manual (Trigger Start)" whereas other entries show either "Automatic" or "Automatic (Delay Start)". The "Hyper-V" entries show a blank in "Status" column, whereas other entries show "Running". Scott, I was mistaken about Hyper-V because I did not check the "Status" column of the "services.msc" column. zip (26.84 KiB) Downloaded 5 times Start ISO file, no options startISOnoOptns.png (23.4 KiB) Viewed 7999 times Using services.msc, as described at superuser dot com slash questions slash 1026651 Would anyone be able to comment on how reliable the compatibility is now? That was almost 3 years ago, when the compatibility was apparently "experimental". Thanks for your advice on what to try next.ĪFTERNOTE: I've read mixed success with VirtualBox compatibility with Hyper-V, which seems to be running on my system. I've uploaded the zipped log file (user name anonymized therein as "User.Name"), along with an image of the lack of options when starting the ISO file. So I powered down without saving the state. I can't seem to power off from within the VM as there is no signs of life from any keyboard or clickpad activity. I've uploaded an image of the GUI at the point where I start the ISO file, and I didn't see an option to "Start the VM from full power off". Would this lead to a dead black screen? If so, how can I get an compatible *.iso file? The Ubuntu download page above doesn't offer any options. In contrast, the Ubunto *.iso file name above indicates AMD. What am I doing wrong? My laptop is an HP EliteBook 840 G6, running i5-8365U. If I banish that message, I get left with only the black screen. I only see a black screen with a single message explaining keyboard capture (tinyurl dot com slash NoInstallUbuntu). Unfortunately, I don't see "Install"/"Welcome" screen. According to the diagram, I should see an "Install"/"Welcome" screen where I select a language and choose to try/install Ubuntu. My problems begins at the top of the second section "Install Ubuntu in VirtualBox", about a third of the way down. It ends with a "Select start-up disk" panel, where I select the *.iso file and click "Start". I don't encounter any problems in the first section of the procedure "Setting up a Virtual Machine in VirtualBox". I got "ubuntu-20.04.3-desktop-amd64.iso" from: ubuntu dot com slash download/desktop. I am following this link to install Ubuntu 20.04.3 LTS on Windows 10: linuxiac dot com slash ubuntu-with-virtualbox
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |