Something strange of the Windows 10 Build 15002 Baseimage
-
ZhengXiaoAi
- Posts: 39
- Joined: Sat May 07, 2016 3:17 am
- Location: Milky Way Train Station
Something strange of the Windows 10 Build 15002 Baseimage
Windows 10 Build 15002's baseimage was leaked some days ago,but why this baseimage can only be installed on Hyper-V?What's the diffience between this baseimage and the Microsoft Offical ISO?Is there some "Additions" for Hyper-V in the baseimage?
I apologize for my grammatical error if it exists, because English is not my primary language.
----------------------------------------
Nothing happen so far,'cause who wants to get burned by the ice? ------ Colder Than Ice by Grant Miller
----------------------------------------
Nothing happen so far,'cause who wants to get burned by the ice? ------ Colder Than Ice by Grant Miller
-
Windows OS
- Posts: 455
- Joined: Tue Jul 08, 2014 9:43 pm
- Location: DLL Hell, United States
- Contact:
Re: Something strange of the Windows 10 Build 15002 Baseimag
By the looks of it, the leaked version of 15002 is identical to the officially released one.ZhengXiaoAi wrote:Windows 10 Build 15002's baseimage was leaked some days ago,but why this baseimage can only be installed on Hyper-V?What's the diffience between this baseimage and the Microsoft Offical ISO?Is there some "Additions" for Hyper-V in the baseimage?
-
BetaNewbie
- Posts: 215
- Joined: Sun Jul 21, 2013 7:38 am
Re: Something strange of the Windows 10 Build 15002 Baseimag
My assumption here, correct me if I am wrong.
The base image is designed for the Desktop App Converter, which is based on Windows Container.
The console session support has been stripped out or disabled ("console" here means local login, and "terminal" means a remote connection). That is why when you boot the image in a physical machine / VM other than Hyper-V, it just stops at the boot screen.
The Hyper-V Enhanced Session is a RDP Connection to the OS effectively.
The base image is designed for the Desktop App Converter, which is based on Windows Container.
The console session support has been stripped out or disabled ("console" here means local login, and "terminal" means a remote connection). That is why when you boot the image in a physical machine / VM other than Hyper-V, it just stops at the boot screen.
The Hyper-V Enhanced Session is a RDP Connection to the OS effectively.