Windows 10: Current Branch for Business updated to Windows 10 1511

Read more:
http://www.winbeta.org/news/current-...indows-10-1511

:)

 

Manual Updates for Windows 10 Creator

Have you considered using CBB (Current Branch for Business)? CBB is one cycle behind.

Configure Windows Update for Business

Configure a machine to use Current Branch for Business with Windows 10

 

1703 current branch or business branch

Log Name: Microsoft-Windows-User Device Registration/Admin

Source: Microsoft-Windows-User Device Registration

Date: 5/31/2017 8:10:27 AM

Event ID: 360

Task Category: None

Level: Warning

Keywords:

User: DESKTOP-C7MSO9M\kenneth

Computer: DESKTOP-C7MSO9M

Description:

Windows Hello for Business provisioning will not be launched.

Device is AAD joined ( AADJ or DJ++ ): Not Tested

User has logged on with AAD credentials: No

Windows Hello for Business policy is enabled: Not Tested

Local computer meets Windows hello for business hardware requirements: Not Tested

User is not connected to the machine via Remote Desktop: Yes

User certificate for on premise auth policy is enabled: Not Tested

Machine is governed by none policy.

See https://go.microsoft.com/fwlink/?linkid=832647 for more details.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-User Device Registration" Guid="{23B8D46B-67DD-40A3-B636-D43E50552C6D}" />

<EventID>360</EventID>

<Version>0</Version>

<Level>3</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000000</Keywords>

<TimeCreated SystemTime="2017-05-31T14:10:27.392639500Z" />

<EventRecordID>164</EventRecordID>

<Correlation />

<Execution ProcessID="7412" ThreadID="7712" />

<Channel>Microsoft-Windows-User Device Registration/Admin</Channel>

<Computer>DESKTOP-C7MSO9M</Computer>

<Security UserID="S-1-5-21-572617098-3236972825-3383922724-1001" />

</System>

<EventData>

<Data Name="Message">Windows Hello for Business provisioning will not be launched.</Data>

<Data Name="DeviceIsJoined">Not Tested</Data>

<Data Name="AADPrt">No</Data>

<Data Name="NgcPolicyEnabled">Not Tested</Data>

<Data Name="NgcHardwarePolicyMet">Not Tested</Data>

<Data Name="UserIsRemote">Yes</Data>

<Data Name="LogonCertRequired">Not Tested</Data>

<Data Name="MachinePolicySource">none</Data>

</EventData>

</Event>













The pc is on a workgroup, not on a domain, none of the 4 pcs on win10 have a home group set up.

Setting the network as to not connect to a business network, restart pc, changes are reverted back again.

1703 continues to try to check the device as to being on a domain.

This is causing issues as to the user login (me) because win10 wants to log me in using a different profile than my microsoft account and loads an imposter login.

This is also taking time to load everything else under the sun because the login has to get special permissions before the system loads.

On desktop loading 15 sec. or more, login 15sec. or more, full desktop, 30sec to 2 min. to load; full completion everything loaded 2 min. + .

The other 3 (2 in use) have 1607 and this is not an issue.

When I set the branch to current, it should stay that way and not keep trying to load the business branch.

Would like to know how different the two are as if their is no drawback to the business branch, I may switch to it.