Windows 10: Microsoft Releases Windows 10 S ISO to Developers, Education Customers

Windows S is intended to be used in Schools or other institutions, mainly used for education. Everything can be serviced and managed in a central place.

As far as I know, you CAN run CMD and PowerShell, but not directly, it must be launched through an app that is Digitally Signed by Windows Store. All the tools are stored locally, but all security critical win32 applications are not available for the normal user. Which is the whole point of this OS.

Security and simplicity.

This OS is NOT intended for the average user. So you, me and other geeks out here, no point in complaining about an OS that is not really intended/targeted for us.

HERE is official MS instructions on Deployment and servicing for Windows 10 S. (The way Schools and institutions work with hundreds of computers the right/intended way)

Simply put, you don't FIX thousands of computers when they are broken, but rather redeploy the latest working and preconfigured image. Takes 10-60 minutes, depending on network and computers on the other end.

 

When you perform a windows update build upgrade (including with Windows 10 S), there is now, in the last few IP builds, a c:\windows.old\$Windows.~BT\sources\windowsold.wim image, which is presumably there for rollback. I intend to see if it is a full image that may be installed on the hardware (in effect, sysprepped for that machine and no user apart from the defaults). The .wim could be mounted and serviced offline, I guess.

Interesting times ahead.

 

Strange thing, since it's geared at schools, is it only comes in OEM and retail versions - no VL licences (in Creator's anyway)

Does someone that has this version installed have this file? I'd like to check if it's been updated in Cloud..

C:\Windows\System32\spp\tokens\pkeyconfig\pkeyconfig.xrm-ms

If it can be upped here, that would be just dandy *Wink

 

Here's the content of C:\Windows\System32\spp\tokens\pkeyconfig\ folder on a clean installed W10 S which was automatically activated based on underlying PRO digital license: pkeyconfig.zip

 

Thanx Kari...

Another strange naming thing I noticed... EnterpriseS (aka LTSB) = No to little UWP vs Windows 10S = only UWP..


Edit: Just checked the file and key configurations are unchanged.

 

On the plus side, Internet Explorer is there, for those that don't like Edge. And Media Player if your not a fan of Groove. Administrative tools is there too, along with Control panel. I'm thinking trouble shooting issues with this version is going to a PITA. Especially activation issues with no access to command prompt or power shell. Those that want to tweak the UI are in for a disappointment to I think. No regedit either, not via search anyway. I haven't gone looking in any folders yet. Just doing a quick search for the usual stuff.

Anybody try to install any peripherals like a printer or all in one manually? My wireless HP Laser Jet was auto detected and installed, which is a good sign. Just wondering if it will let you run the printer utilities that come bundled with said items. I don't have a disk handy to try it myself, I never install that stuff and have no idea if I even kept the disks, lol.

EDIT: Just noticed HP Smart "Trusted Store App" installed in the background. Good, I guess?

 

I'm starting to repeat myself. Only tools that come digitally signed from Windows Store can be run. That includes ALL MS provided drivers and applications (mostly UWP). If you try to install or run any app from elsewhere but Windows Store or WU provided binaries it won't run.

 

Yah, I agree.. it's gonna take some getting used to, to troubleshoot in UWP... the error codes are different and 'concealed' whereas with Win32 there are components to convert them to a sensible description...

Having said that, Google's Chromebook works much the same... and seems trouble-free

 

Ok, fine, chill out dude. I'm just posting some observations. Is this the way it's going to be for the rest of this thread? Pick everything I say apart?

 

Found regedit, as expected double clicking gets a "this mode of Windows only runs verified Apps etc." And a still want to run it, see how' option that takes you to a upgrade to 10 pro screen.

 

I'm getting the occasional "script error" message. Just got one when opening services from administrative tools. Object doesn't support this property or method. You can continue though. Not sure what that all means?

 

@alphanumeric I am sorry, not trying to pick on anyone.

Windows 10 S is same binaries as Windows 10 Pro, except for the policy configuration and some re-routing of messages to Upgrade to Windows 10 Pro, if you want to run binaries that are not digitally signed by Windows Store.

If you upgrade to Pro, only thing that change should pretty much be the policy configuration and maybe some other small tweaks. Nothing to Windows internal related binaries should be downloaded during the upgrade process.

 

I haven't had any real issues as of yet. Some script errors but they don't seem to be stopping anything from working? I've only had it up and running for day. Today is the first real chance I've had to poke around. I kind of like to know what works and what doesn't.

 

There exist a so called Bridge, that allows you to use a Signed Windows Store app to launch binaries like CMD and PowerShell.

If you are a software developer, this kind of information is important.

 

Right now I'm just poking around to see if something slipped threw the cracks. We all know people are going to try and do things they weren't meant to do. And I'm looking for things that are maybe broken. Those script error for example. I get it, its a custom version of Windows 10 Pro. If there was a wave the white flag smiley it would be here. ><