I have a Windows 10 machine. Recently I have installed Hyper-V 2016 server on my machine. From then whenever I start my system I only see a blue screen with various commands. I do not see any other thing other than that. Now how can I go back to my normal Windows machine?
See this image for reference:
you had Windows 10 installed on your machine now you have Microsoft Hyper-V Server 2016.
I assume you downloaded an ISO and installed that one. Whereas within Windows 10 you only have to activated a feature called Hyper-V.
Grap your latest Backups and install Windows 10 back onto your machine.
KR
Guenther
Related
These are the details of my physical server:
Windows Edition: Windows Server 2008 R2
Processor: Intel Xeon
System Type: 64 bit operating system
I am trying to run CentOS 7 using VMware Workstation Pro Version 14.
After creating the VM, when trying to run it I get a black screen in the console.
while exiting from the console view you can see actually CentOS 7 installation and leaving it running will actually successfully install CentOS and will ask you for the language but I can't choose anything from outside the console view, neither inside the console view(black screen).
Please note the following:
I tried both CentOS 7 minimal and everything isos downloaded from the CentOS official website
I enabled Intel Virtualization in the BIOS as requested in VMWare Community Website
I started the VMWare Authorization Server in the services section as mentioned in VMWare Community Website
I have no anti-virus running
I tried using VMWare Player instead of VMWare Workstation and the same error occurred
This is the complete VMWare log file
Im totally new to Google Cloud. I got free uses for some time from google.
I want to setup a lab. So I want to install Windows 7 on Google Cloud.
Thanks
The image for Windows 7 is not available, you can create a custom image, upload it and then create an instance with that image, but honestly I would not follow this path if you have just started and you want only to run a Windows server.
So, if you don't really need Windows 7 for some reason and you want to run a Windows virtual machine the easiest thing to do is to create an instance using one of the available images:
Windows Server version 1709 Core for Containers (Beta)
Windows Server version 1709 Core
Windows Server 2008 R2
Windows Server 2012 R2 Core
Windows Server 2012 R2
Windows Server 2016 Core
Windows Server 2016
In order to do so go to the Console, enter in Compute Engine, VM instances, click on create instance, at this point from the tab that will be opened select the Windows image that you prefer and set up the machine as you like. Wait some minute and you will be able to connect to it through RDP.
Note that there is a Quickstart guide in order to help you in the process.
WSL stands for Windows Subsystem for Linux. Is it even available on EC2?
All the guide I found talks about Windows Desktop, not server.
According to the docs: https://aws.amazon.com/about-aws/whats-new/2018/05/amazon-ec2-now-offers-windows-server-version-1709-and-1803-amis/
You can now use 1803 update with support for WLS.
As of August 2017, WSL is available on Windows Server insider builds..
Although I haven't tried it, I assume you could start a Windows Server 2016 instance and enable Windows Insider updates.
The installation guide for installing WSL on Windows Server is here.
I am using Amazon windows 10(2016 server) server for running my application.I need to run VMware in windows but it shows,
VMware Player and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Player.
I did not install Hyper-V even though VMware is not working, showing above statement.
If Hyper-V is installed you will need to uninstall it for VMWare to run, you can do this by:
Press the Windows key + X
Then go to `Programs and Features`
Click Turn Windows Features on or off
Open Hyper-V
Toggle if off and then click okay.
Note: you may need to restart the virtual machine afterwards.
I've already tried running Docker on a Windows 10 Virtual Machine without any success. I understand why, so I've given up trying to enable this. However, it's got me thinking about Windows Server 2016. As I understand it, Windows Server 2016 has docker included as a component/service, instead of an 'Add On' as it is in Windows 10. Are there any reasons why a Microsoft Server 2016 Virtual Machine would not support docker? This is more for convenience than anything else. Dual-booting with windows 10 isn't a major issue and we've done that, but it does mean in certain circumstances I have to reboot to windows 8 for certain organisation-specific content that I can't access in Windows 10.