I'm trying to install Windows Server 2012 R2 on Virtualbox but I get this error all the time:
Proccessor: Intel(R) Core(TM) i5 CPU
System type: 64-bit
ISO file: en_windows_server_2012_x64_dvd_915478.iso
I've tried many things and had no result, I tried on another computer but got the same error.
When creating a new VirtualMachine I used "Windows > Other Windows" and created a new VDI
Common problem. You have to activate virtualization in your bios. If doesn't matter if you have a 64 bits CPU if you don't have the virtualization activated. This is an example.
Related
npm install
audited 17250 packages in 7.466s
26 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
My System Info:
1.OS Name Microsoft Windows 10 Home Single Language
Version 10.0.18363 Build 18363
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-7CV9HTK
System Manufacturer HP
System Model HP ENVY Laptop 13-ah1xxx
System Type x64-based PC
System SKU 5HZ05PA#AKL
Processor Intel(R) Core(TM) i7-8565U CPU # 1.80GHz, 1992 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Insyde F.12, 11/8/2018
SMBIOS Version 3.0
Embedded Controller Version 69.72
BIOS Mode UEFI
BaseBoard Manufacturer HP
BaseBoard Product 850B
BaseBoard Version 69.72
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "10.0.18362.387"
User Name DESKTOP-7CV9HTK\Hanifullah Jamalzai
Time Zone Afghanistan Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.8 GB
Available Physical Memory 9.89 GB
Total Virtual Memory 18.2 GB
Available Virtual Memory 10.3 GB
Page File Space 2.38 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
Npm is recognized on cmd but not on vscode?
Assuming you are using windows, you need to update the path in environment/user variables AND restart vscode for it to recognize the changes.
I had Yarn Package Manager which is an alternative to npm. The packages you are trying to install can not be installed with npm, "npm install" will not work because it is not the format used by yarn when you are trying to install some package.
I am trying to get Oracle VirtualBox (6.1) to run on a Windows 10 (1909 - Build 18363.535) VM running on Server 2012 R2 (6.3 - Build 9600).
I can install and create a VM in Oracle VirtualBox. Only 32-bit OS's are available. When i try to start the OVB VM i get the following error:
WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature. (VERR_NEM_NOT_AVAILABLE).
VT-x is not available (VERR_VMX_NO_VMX).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
I cannot enable the Windows feature Hyper-V Platform. And when i check the SystemInfo : Hyper-V Requirements i only have the following line:
A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Is there a way that i can run OVB on a Windows 10 VM running on Server 2012?
Turns out Windows Server 2012 doesn't work, but Server 2016 does. Tested on another server, working.
I need to install Docker on my pc with Windows 10 home. I read that I can only install Docker Toolbox. Is there any way to have the latest Docker version instead without upgrading my pc to windows 10 pro?
Thanks
Update
Docker can now be installed on Windows 10 Home (version 2004 or higher).
Refer to this article for installation instructions
https://docs.docker.com/docker-for-windows/install-windows-home/
Old Answer
Docker for Windows requires Hyper-V, and Hyper-V requires Windows 10 Pro (or Windows Server). So no, you can't run Docker without upgrading.
https://docs.docker.com/docker-for-windows/install/
README FIRST for Docker Toolbox and Docker Machine users: Docker for Windows requires Microsoft Hyper-V to run. The Docker for Windows installer enables Hyper-V for you, if needed, and restart your machine.
https://learn.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v
Check Requirements
Windows 10 Enterprise, Professional, or Education
64-bit Processor with Second Level Address Translation (SLAT).
CPU support for VM Monitor Mode Extension (VT-c on Intel CPU's).
Minimum of 4 GB memory.
The Hyper-V role cannot be installed on Windows 10 Home.
You can now install Docker Desktop on Windows Home machines using the WSL 2 backend. Docker Desktop on Windows Home is a full version of Docker Desktop for Linux container development.
https://docs.docker.com/docker-for-windows/install-windows-home/
Install Windows 10, version 2004 or higher.
Enable the WSL 2 feature on Windows. For detailed instructions, refer to the Microsoft documentation.
https://learn.microsoft.com/en-us/windows/wsl/install-win10
The following hardware prerequisites are required to successfully run WSL 2 on Windows 10 Home:
64 bit processor with Second Level Address Translation (SLAT)
4GB system RAM
BIOS-level hardware virtualization support must be enabled in the BIOS settings. For more information, see Virtualization.
https://docs.docker.com/docker-for-windows/troubleshoot/#virtualization-must-be-enabled
Download and install the Linux kernel update package.
https://learn.microsoft.com/en-us/windows/wsl/wsl2-kernel
I'm new on LG smart TV apps. I've installed the SDK provided by LG (Oracle Virtual Box, Safari, Eclipse, sdk itself).
Now everything is running, but when I try to launch the emulator, a remote control is displayed, and on the virtualbox window, I see an error and no emulator is launched.
This is my plataform:
Windows 7 on a intel i7, 8 gb ram
Virtual Box 4.1.18 (I've installed 4.2.4 before, but sdk installer replace it to 4.1.18)
Safari 5.1.7
Java JRE 1.6
LG Smart TV SDK 3.0.0
This is the log generated by Virtual Box:
VirtualBox 4.1.18 r78361 win.amd64 (Jun 5 2012 15:58:23) release log
00:00:05.144 Log opened 2015-09-28T15:09:54.564361900Z
00:00:05.144 OS Product: Windows 7
00:00:05.144 OS Release: 6.1.7601
00:00:05.144 OS Service Pack: 1
00:00:05.144 Host RAM: 7926MB RAM, available: 864MB
00:00:05.144 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:05.144 Process ID: 12536
00:00:05.144 Package type: WINDOWS_64BITS_GENERIC
00:00:05.145 Installed Extension Packs:
00:00:05.145 None installed!
00:00:05.156 Power up failed (vrc=VINF_SUCCESS, rc=E_FAIL (0X80004005))
00:00:05.439 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={The virtual machine is not powered up}, preserve=false
Is there any known issue about this? What is the reason because "Power up failed"? How can I fix the VM? Does this software really works on Windows?
Thanks!
I would try 4.2.18 and make sure you are installing the correct SDK for your OS (x64/x32).
You can uninstall VBox and reinstall if needed and again check your architecture
Trying to test a new CSP under Win 7. Set the boot config to allow kernel debug, run WndDbg and select file:kernel debug and set to local. Attempting to use signtool with my new CSP still results in signature failure check. Environment is:
OS Name: Microsoft Windows 7 Home Premium
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
System Model: Dell System Inspiron N7110
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 42 Stepping 7 GenuineIntel ~2501 Mhz
BIOS Version: Dell Inc. A09, 11/18/2011
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Any thoughts on why the presence of the kernel debugger is not preventing the signature check on the test CSP? Does that setup only work in a remote-debug environment?
You'll need a remote debugger to disable the signature check.
There are various mechanisms such as 1394 (FireWire) or Serial Cable by which you can can connect the second computer for remote debugging.
If your CSP can run in a VM, then that would be an option too if you just have the one machine.