Microsoft Releases Windows 10 S ISO to Developers, Education Customers

Superfly said:

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

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.

slicendice said:

@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.

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. ><

alphanumeric said:

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?

It's still Win32 based - they have 'normal code' calling API's from XML... which it shouldn't - it still needs refinement... I dunno why this was/is not part of Insider, TBH.

Superfly said:

It's still Win32 based - they have 'normal code' calling API's from XML... which it shouldn't - it still needs refinement... I dunno why this was/is not part of Insider, TBH.

Agree!

Superfly said:

It's still Win32 based - they have 'normal code' calling API's from XML... which it shouldn't - it still needs refinement... I dunno why this was/is not part of Insider, TBH.

I had been looking for this since it was announced with no luck. Then bam there it was. Same deal for Windows 10 Pro Education. It was announced a while back. No sign of that anywhere.

The option to opt into the Insider Program is there in Settings > Update & Security > Windows Insider Program. I agree, it should have been released to the program first though. I'm going to refrain from clicking get started for now though. I want to poke around some more with the stock setup before I see if will actually update to an insider build.

Looks like I'm stuck with "Microsoft Basic Display Driver". Update driver from Device Manager just gets a Best driver already installed message. Windows update doesn't find anything either. Trying to run the NVidia driver manually is blocked. In Windows 10 Home, Pro etc Windows Update installs the required NVidia driver in the background. That leaves me stuck at 1024 x 768 instead of 1440 x 900. 1440 x 900 is not listed as an option, 1280 x 1024 is the highest listed.

Weirdly though, I could point Windows to my ASUS ATK driver folder on my thumb drive and it accepted that. My unknown device disappeared and all am ACPI stuff showed up.

Got my NVidia GT 610 back. :) I went to the NVidia site and downloaded the latest Windows 10 driver for my card. It's one big exe file so I ran that (on my 10 Pro PC) and let it extract itself to a folder. Then canceled the install when it started scanning hardware. Then I took the whole lot and copied it to my thumb drive. Then plugged that into my 10-S PC. Opened Device Manager, did the update driver, Browse my computer, and pointed it to the "Display.Driver" folder on my thumb drive. It accepted it and went to updating drivers. Took a while but now I have the correct resolution for my monitor. That folder is full of inf files, which is what I think its looking for?

Did some more poking around and found you can run diskpart from the Run box. cmd is blocked though.