[1703, cu] Windows 10 Creators Update (v1703) now available to download

[sted]

ran 1703 on one machine. I already knew about the lock screen not listening to GPO but now our start menu wont even open (nor search) - however it DOES populate my taskbar with the correct icons! "allow cortana" is "not configured" so im not disabling that. Up till now I had no issues with start menu in 1607. sigh. here we go again.

bt start menu not working do you mean fully populated but greyed out? if so i think ive narrowed it down to applocker policies ive rewritten mine from scratch and am testing again as i thought id cracked it and it worked fine with no applocker policies applied but even a cutdown version of my old one gave me issues so i whacked rsat on a 1703 machine and built a new default applocker policy im in process of building a 2nd test laptop to see if thats fixed it

[eddyc]

Think that's fixed it - our sequence rebooted and continued quite happily.....

So, at the start of the State Restore section in our task sequence I created firstly a 'Run Command Line' which does a ' powershell.exe -command "Set-ExecutionPolicy Bypass" ' - this ensures that the PowerShell script will execute, then followed up with a Powershell script that has ' %ScriptRoot%\Set-AutoLogon.ps1 '

Inside the Scripts folder of the Deployment Share, I have the following PS script called Set-AutoLogon.ps1...

 

$RegPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"Set-ItemProperty $RegPath "AutoAdminLogon" -Value "1" -type String  Set-ItemProperty $RegPath "DefaultPassword" -Value "PUT YOUR LOCAL ADMIN PASSWORD HERE" -type String

 

Now, with any restart step we have in our sequence, the machine does log back in again and continues (we find we need to put a restart in before we attempt to install things like Adobe CS6).

 

Pete

 

Hello @FragglePete - This doesn't work for me. I wonder if it is because I mask our local administrator account as ladmin rather than Administrator - Any ideals or suggestions please?

 

Thanks in advance!

[KK20]

bt start menu not working do you mean fully populated but greyed out? if so i think ive narrowed it down to applocker policies ive rewritten mine from scratch and am testing again as i thought id cracked it and it worked fine with no applocker policies applied but even a cutdown version of my old one gave me issues so i whacked rsat on a 1703 machine and built a new default applocker policy im in process of building a 2nd test laptop to see if thats fixed it

 

Nope, as in click and nothing happens, no window, no movement; a quick circle of "busy" and nothing. I managed to figure out that the search and taskbar works if you DONT click the start menu. As soon as you click the start button then search and taskbar buttons stop working until you log out/back in. There will be a GPO no doubt stopping this so i've passed it over to the minion to disable all the GPOs and find the offending one....

[FragglePete]

Hello @FragglePete - This doesn't work for me. I wonder if it is because I mask our local administrator account as ladmin rather than Administrator - Any ideals or suggestions please?

 

Thanks in advance!

Could well be, but I guess you could try adding a DefaultUserName key with your local admin account name as well. Top of my head it would be something like.....

 

$RegPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"
Set-ItemProperty $RegPath "AutoAdminLogon" -Value "1" -type String  
Set-ItemProperty $RegPath "DefaultPassword" -Value "YOUR PASSWORD HERE" -type String
Set-ItemProperty $RegPath "DefaultUserName" -Value "ladmin" -type String

 

Our MDT Task Sequence is chugging alone quite nicely now. Not sure why Microsoft had to put a voice into the sequence on first reboot saying it's "Connected, looking for updates" - going to be odd over Summer hearing that blare out around the school!

 

Pete

Edited May 23, 2017 by FragglePete

[clockend25]

Just noticed this too. Found this, known bug:

 

https://social.technet.microsoft.com/Forums/en-US/c59091a7-0fae-4dca-8baa-193c0906efe1/mdt-8443-w10ent-1703-auto-login-and-wsus-issue?forum=mdt

 

I'm putting in an additional powershell step in at the moment; just running through now to see if it will work.

 

Pete

 

 

Nice one!

[eddyc]

Ah, we've got to the bottom of it here... Because our password contains special characters (including a $ sign), we had to pass the password as a variable in the code. The escape character for powershell is the grave-accent (`) so we added $pass = "Pa55w0rd`$" and then used the variable $Pass in the code as shown below. Works a charm.

 

$Pass = "Pa55w0rd`$"
$RegPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" 
Set-ItemProperty $RegPath "AutoAdminLogon" -Value "1" -type String 
Set-ItemProperty $RegPath "DefaultPassword" -Value $Pass -type String

[Arthur]

Ah, we've got to the bottom of it here... Because our password contains special characters (including a $ sign), we had to pass the password as a variable in the code. The escape character for powershell is the grave-accent (`) so we added $pass = "Pa55w0rd`$" and then used the variable $Pass in the code as shown below.

@eddyc. You don't need to escape the $ if you use single quotes around the password. Double quotes allow variable expansion while single quotes do not.

 

$Pass = 'Pa55w0rd$'
$RegPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" 
Set-ItemProperty $RegPath "AutoAdminLogon" -Value "1" -type String 
Set-ItemProperty $RegPath "DefaultPassword" -Value $Pass -type String

 

See also: https://msdn.microsoft.com/en-us/powershell/reference/5.1/microsoft.powershell.core/about/about_quoting_rules

[garethEds]

I really want to move the school to Windows 10, but with all these issues on top of what other hassles I read here on Edugeek, I really think sticking with Windows 7 is best for another year (from September).

 

Gareth

[mukz]

I really want to move the school to Windows 10, but with all these issues on top of what other hassles I read here on Edugeek, I really think sticking with Windows 7 is best for another year (from September).

 

Gareth

 

I thought the same. Started a test VM up for staff to test it out for me in there own time. So far no issues. Everything seems to work the way we want!

Although to be fair i haven't updated to the creators build yet. Will do this when i am back from hols and if goes well we plan to deploy to an IT Suite and the Computer Science Department.

 

We have some Sixth Formers who help me test the hell out of things. (One eager beaver even helped roll out papercut mf)

[kennysarmy]

I really want to move the school to Windows 10, but with all these issues on top of what other hassles I read here on Edugeek, I really think sticking with Windows 7 is best for another year (from September).

 

Gareth

 

I'm certainly in no rush either, certainly not for a mass site wide deployment, but I think next academic year from September I might push a few text PC's out to see what happens. It could be a softly softly roll-out, it's ONLY the OS!

[alfatec]

We went full 100% Windows 10 last year on 1511. Now they are saying that 1511 will go end of life late 2017 but version 1703 still has loads of issues. We do not have any issues with 1511. The main issues seem to have come

from 1607 and 1703. Still waiting for fixes on 1703 before we can re-build a new image for that. I think the option of LTSB even though it is missing a few features might be looking a good option.

[mavhc]

So far there's about 3 apps that are Windows 8/10 only that I've seen that might be useful, so not a great rush to upgrade everyone.

 

In general I'm more worried that Microsoft want to kill Windows Server and GPOs and have everyone using AAD, Intune, and that Set Up School PCs thing

[eddyc]

Has anyone found the lock screen hotfix yet? It was apparently released yesterday but I am struggling to find the KB number anywhere.

 

Cheers, eddyc

[Arthur]

A fix for the Secure Boot issue with the Windows ADK for Windows 10 v1703 is now available.

 

A fix for this issue is now available. Download this file, extract the contents, and follow the instructions in the readme file. NOTE: this driver update for the Windows ADK for Windows 10 version 1703, only addresses the specific issue described below. There is also a known issue with 802.1x (dot3svc) which is not included in this update.

 

 

A PowerShell script to automatically download and install the fix is available from here...

 

https://gist.github.com/keithga/6a64abb048d885ea7c5f096c319f38b8

[guinfan72]

I'm getting this same error, skip works. Problem is, I don't want to sit around waiting for labs of computers to get to this point and hit skip over and over. Has anyone found a fix for this issue?

 

I've come across a couple of problems with this new version so far. I get a "Something went wrong. You can try again, or skip this for now." during the OOBE stage. I've created a new answer file with a new catalog file but still no luck. Setup seems to complete ok.

 

Looking at the log files it seems to be this showing the problem:

 

2017-04-07 16:59:34, Info [CloudExperienceHostBroker.exe] Failed to load oobe.xml file at C:\Windows\system32\oobe\info\oobe.xml with hr=0x80070003

2017-04-07 16:59:34, Info [CloudExperienceHostBroker.exe] Failed to load oobe.xml file at C:\Windows\system32\oobe\info\default\oobe.xml with hr=0x80070003

2017-04-07 16:59:34, Info [CloudExperienceHostBroker.exe] Failed to load oobe.xml file at C:\Windows\system32\oobe\info\242\oobe.xml with hr=0x80070003

2017-04-07 16:59:34, Info [CloudExperienceHostBroker.exe] Failed to load oobe.xml file at C:\Windows\system32\oobe\info\default\2057\oobe.xml with hr=0x80070003

2017-04-07 16:59:34, Info [CloudExperienceHostBroker.exe] Failed to load oobe.xml file at C:\Windows\system32\oobe\info\242\2057\oobe.xml with hr=0x80070003

 

Start menu will revert back to default layout instead of the customised one created in audit mode. This worked fine in the previous build.

[gshaw]

In general I'm more worried that Microsoft want to kill Windows Server and GPOs and have everyone using AAD, Intune, and that Set Up School PCs thing

Indeed, there doesn't seem to be much benefit at all moving fixed PCs to AAD \ InTune but it's a nice revenue generator for MS.

[Arthur]

@guinfan72 @hailstorm

 

Your errors look like they might be related to the issue described in the article below (despite the 0x80070003 code indicating it's related to driver installation)....

 

www.mcgowan.id.au/blog/fix/fix-windows-10-1703-something-went-wrong-during-osd/

 

There is a lot of info out there now regarding this error with various fixes, but since I now having a working solution this update to the post is what worked for me.

 

• Restricted Groups is still being used to lock down the administrators group
  
• The UAC settings are on the most strict setting (always prompt on the secure desktop)
  

These were hard requirements for my situation, to pass security audits. Relaxing either or both of these settings has resolved the issue for some people, but was not an option for me.

 

What appears to be working :

 

• Using a non-captured reference WIM file. Previously I had a captured WIM from a build & capture task sequence. I have changed this to using the default install.wim from installation media and doing the minimal customisations in the deployment TS
  
• Applied May 2017 updates to the install.wim via offline servicing
  
• Setting SkipMachineOOBE and SkipUserOOBE to true on the unattend.xml
  

I did test each of these in isolation, and they didn’t work. The install.wim didn’t work with or without the updates, and the unattend changes didn’t work on the previous captured WIM. This current setup appears to be working.

 

Another thing that can cause the "Something went wrong" message is Windows automatically installing drivers in the background during OSD...

 

https://jsiewert.wordpress.com/2017/05/26/automatic-driver-updates-during-mdt-deployment-of-windows-10-1607

[Arthur]

See also:

 

Windows 10 1703 OSD - Fixing all the things

 

There are multiple issues being reported with 1703 OSD relating to how the OS does the OOBE in a deployment scenario. This guide will take you through fixing the nuances such as fixing the cleanup of the DefaultUser0 profile, getting past the "Just a moment.." screens during imaging, and fixing issues where the post-image "Checking for Updates..." fails out to the login screen.

 

[...]

 

Fixing OOBE screens ("Just a moment..." and "Checking for updates")

Windows 10 1703 is unique in that you must use the following unattend file to eliminate the OOBE prompts from running during OSD: https://github.com/winadminsdotorg/SystemCenterConfigMgr/blob/master/OSD/Configuration/unattend.xml

 

Also make sure you don't have any group policies controlling the following UAC group policy:

 

Computer>Policies>Windows Settings>Security Settings > Local Policy > Security Options > User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode GPO to Not Configured.

 

(Note: If you are using the security baseline from the Security Compliance Manager, it configures this GPO)

 

   
       
           
               true
               true
               true
               true
               true
               Work
               1
               true
               true
           
       
       
           
               true
               true
               true
               true
               true
               Work
               1
               true
               true
           
       
   
   

[Arcolite]

I haven't seen it mentioned earlier in this thread, but for anyone else who uses the of the Unattend.xml, please note that this is broken in 1703 pre June 2017.

 

There's a fix for it in the June 2017 Cumulative Update - https://support.microsoft.com/en-in/help/4022716/windows-10-update-kb4022716

Addressed issue where, if you specify an auto-logon configuration in Unattend.xml, auto-logon only works on the first logon, but will not work again when the device is restarted.

 

I'm currently slip-streaming the July update into our media so we can resume building our more complicated departmental images.

That serves me right for not slip-streaming anything new since May.

[mavhc]

In future news: Fall Creators Update to be delayed 6 months for Australian users

[DJ-1701]

In future news: Fall Creators Update to be delayed 6 months for Australian users

 

As 'Fall', which is Autumn... is 6 months later in the US? Sure this shouldn't be in the punny thread?

[Arthur]

Good news!

 

Windows 10's next feature update to be called the 'Autumn Creators Update' in some countries

 

Back in May, Microsoft announced that the next major update to Windows 10 would be called the "Fall Creators Update". While the name isn't exactly what one would call "imaginative", it coincided with update's release schedule, which is September 2017.

 

However, it now appears that the feature update won't be known by the same name globally. In fact, it will be released as the "Autumn Creators Update" in some countries.

 

As spotted by Windows Central, Microsoft has quietly changed instances of "Fall Creators Update" to "Autumn Creators Update" on its dedicated page in the UK.

[mavhc]

If they could give each version just one name/version number instead of 3, that would be a start