[1809, ou] Windows 10 v1809 released

[Arthur]

what log is that from, smsts?

The log created by Remove-AppxProvisionedPackage in the PowerShell script quoted above.

 

I removed the appx package the way I always do during OSD and it seamed to work. I didn't check the log for errors though.

After you login, do you see any apps that you had previously removed during OSD or are they all gone?

 

This bug may only affect removing apps from a mounted .wim (offline).

[ADMaster]

All the apps I remove via the OSD script were gone. So it must only effect mounted wim.

[Arthur]

it must only affect mounted wim.

It was Mount-WindowsImage's -Optimize parameter that was causing this issue.

 

https://twitter.com/jarwidmark/status/1063594435252875265

 

[Arthur]

Security baseline (FINAL) for Windows 10 v1809 and Windows Server 2019

 

Microsoft is pleased to announce the final release of the security configuration baseline settings for Windows 10 October 2018 Update (a.k.a., version 1809, “Redstone 5” or “RS5”), and for Windows Server 2019.

 

For now, download the content here: Windows-10-1809-Security-Baseline-FINAL. It will be posted to the Security Compliance Toolkit download site very soon.

[Norphy]

One interesting thing about 1809:

 

Windows 10 now sees the touchpad on my MacBook Pro as a precision touchpad so I get all of the Windows 10 touchpad gestures. It didn't do that before without dodgy hacked third party drivers.

[Arthur]

New 1809 issue (although it's more Intel's fault than Microsoft's)...

 

https://support.microsoft.com/en-gb/help/4464619

 

[ADMaster]

I have a weird update to my 10 minute first log in issue.

It only appears to effect the main domain admin account.

If the domain admin account is the first user to log on after an image it takes 10 minutes, all other users first log in takes 2 minutes.

 

If another user logs on first after an image, then the domain admin first logon is only 2 minutes too.

 

Can anyone else reproduce this or have suggestions to fix this.

Yes I know its not good practice, but I'm an IT department of 1.

[jmak]

Yes I know its not good practice, but I'm an IT department of 1.

 

A bit off topic; I'm in the same situation. I have two accounts and only use my domain admin where essential. I only find it a very minor inconvenience. I can operate RSAT as a different user and can remote into other machines with my domain admin account. It's very rare that I need to login to a client machine with a domain admin account account.

[ADMaster]

@jmak,

Can you reproduce this issue? Image a VM with 1809 and log in for the first time as the main default domain admin account.

 

Security / admin accounts have been discussed several times already, so I'll be brief in an attempt to keep on topic. If you wish to discuss further we can take it to another thread or PM.

 

I've worked to improve security, enable cred guard, create gmsa's, use a dedicated client admin account for deploying software etc. I've just always logged on with the administrator account after an image. I can think of a few reasons why I did this in the past, but things have changed and those reasons are no longer valid. Its just a bad habit at this point.

 

If I'm imaging 1 PC for a user, that is the account I'd use to make sure everything installed correctly and also when testing images in a VM. I don't do this when I image a full suite so I didn't want users getting a first logon of 10 minutes after image and also didn't know if it indicated other underlying problems with my image.

 

Now that I know the cause / fix I can move forward and just not use the admin account. However I'm still curious if anyone else can reproduce the issue.

[mavhc]

Weird long logins after updating to 1809, student noticed if while "preparing windows..." is showing you ctrl-alt-del and then escape, you get to the desktop. Now should I blame Impero or Microsoft?

[mullet_man]

Weird long logins after updating to 1809, student noticed if while "preparing windows..." is showing you ctrl-alt-del and then escape, you get to the desktop. Now should I blame Impero or Microsoft?

 

I've noticed that on versions before 1809, I haven't tested 1809 as yet (due to the issues)

 

It could be that 1809 it's made the issue worse?

 

Anyway am testing a laptop now with a IPU with SCCM. Lets see if it delete's the documents haha

[jmak]

@ADMaster I've got enough broken things without introducing 1809 to my network [emoji23]

 

I've got 1803 on all machines and I'm hoping to scrape through to 1909 so that I can get onto one of the 30 month releases.

[mullet_man]

Straight away I've got the mapped drives issue.

 

Am not sure I'll push this version out anyway, 1803 seems stable enough.

 

Am still trying to get back staff laptops with 1607 on so I can update them!!

[free780]

I think with laptops you just have to let them update themselves from Microsoft Update after you've tested everything.

[thatley]

Straight away I've got the mapped drives issue.

 

Am not sure I'll push this version out anyway, 1803 seems stable enough.

 

Am still trying to get back staff laptops with 1607 on so I can update them!!

 

 

Yes I reported this back on page 3 of this thread - I'm staying well clear of 1809!

[mullet_man]

I think with laptops you just have to let them update themselves from Microsoft Update after you've tested everything.

Am hoping that a some point I'll have my IPU task sequence at a point where I can let it do it in the wild, am at a point my where task sequence

 

Updated the BIOS

Upgrades Windows

Applies the latest driver packs

 

Am lucky as am all Dell laptops for staff so with the awesome Driver Automation Tool it adds the latest BIOS and drivers to SCCM and I just need to adjust my task sequence.

 

It helps too I've got about 5 different models so not too many to adjust a few things here and there.

[rosslaing]

Am still trying to get back staff laptops with 1607 on so I can update them!!

 

When it gets to this point we just disable the Computer accounts in AD. Seeing as they use direct access if they have them at home, they are soon handing them in again to get 'fixed'!

[mullet_man]

When it gets to this point we just disable the Computer accounts in AD. Seeing as they use direct access if they have them at home, they are soon handing them in again to get 'fixed'!

 

I've not got to that point as yet but it's something I might have to do soon.

[MYK-IT]

Windows 10 1809 / Server 2019 Servicing Stack Update

https://support.microsoft.com/en-us/help/4469342/november292018kb4469342osbuild17763167

[Arthur]

Windows 10 1809 / Server 2019 Servicing Stack Update

Small correction...

 

KB4470788 = Servicing Stack / KB4469342 = Cumulative Update

 

Microsoft has finally fixed the drive mapping, brightness and default app issues...

 

[Fazza]

Small correction...

 

KB4470788 = Servicing Stack / KB4469342 = Cumulative Update

 

Microsoft has finally fixed the drive mapping, brightness and default app issues...

 

 

Do these replace previous ones such as Servicing Stack Update KB4465664 and Cumulative Update KB4467708 or do I need to do both lots?

[Arthur]

Do these replace previous ones

They do.

[Arthur]

PSA: "NVIDIA Installer cannot continue" on Windows 10 October 2018 Update and How To Fix It

 

For those doing a fresh install of Microsoft's latest Windows 10 operating system (version 1809 October 2018 Update), you may encounter an issue with NVIDIA graphics drivers. Namely, a message may pop up when you install the graphics driver, telling you "The standard NVIDIA graphics driver is not compatible with this version of Windows". The issue is caused by the operating system automatically installing the GeForce 398.36 DCH graphics driver through Windows Update, immediately after first log-on. DCH drivers are also known as "Universal Windows Driver", "UWD", "DCHU", and "Declarative, Componentized, Hardware Support App", and leverage the Windows UWP platform for driver control panels while promising simpler updates and maintainability.

 

If networking is available during the Windows 10 installation, the operating system will automatically look for a graphics driver on Windows Update, which is a good thing, as it simplifies the setup process for the majority of users. At this point, everything will appear to be fine, however, once you attempt to update from that driver to the newest version from NVIDIA's driver download page, the error will appear. This is highly frustrating for some users, who have been reporting the issue on several online forums, including NVIDIA's own, with little attention paid thus far from their developers. We encountered the problem ourselves today, during the setup of our 2019 SSD review benchmarking install and got motivated to investigate this further.

[caffrey]

Another windows 10 issue (Found over at reddit) Calculator is broken now...

 

[mullet_man]

Am keeping with 1803, seems to work fine and not had any issues. Might look to upgrade people to 1809 at some point but am going to skip making an image of 1809 I think.

 

Think I'll make a new image yearly so next one will be 190X and then just use SCCM to upgrade to other releases.

 

That's my plan at the minute anyway