Windows 10 UAC prompt upon logon for standard users

[lafleur1977]

Hello,

 

I am currently working on deployment for windows 10 and so far so good, got deployment working well with MDT and I am deploying a vanilla windows 10 1809 image. I have hit a snag when testing staff/student accounts where they get a UAC prompt when they login. The problem also affects a standard local user too but admin accounts don't receive the UAC prompt.

 

Has anyone had this before?

 

Thanks

Edited June 20, 2019 by lafleur1977

[MartinByard]

I had this - if its the same problem I had, then to fix it I needed to add the relevant language Feature's on Demand extra's (handwriting, speech etc.). This was most likely due to using the international iso to build the image, but specifing EN-GB as the language ...

[lafleur1977]

Thanks, I thought it might be something to do with the language as I saw some info about it when googling the error. I've used eng international too. How did you go about adding the features on demand?

[MartinByard]

Download the language pack iso and the features on demand iso from the MS VL site, extract the ones I needed and added them to a package in SCCM (should be similar with MDT) and then had a run command line step in the task sequence that ran DISM and installed the features.

 

The DISM step(s) are specifically:

Dism /Online /Add-Package /PackagePath=".\Microsoft-Windows-Client-Language-Pack_x64_en-gb.cab"

and

Dism /Online /Add-Package /PackagePath:.\Microsoft-Windows-LanguageFeatures-Basic-en-gb-Package~31bf3856ad364e35~amd64~~.cab /PackagePath:.\Microsoft-Windows-LanguageFeatures-OCR-en-gb-Package~31bf3856ad364e35~amd64~~.cab /PackagePath:.\Microsoft-Windows-LanguageFeatures-Handwriting-en-gb-Package~31bf3856ad364e35~amd64~~.cab /PackagePath:.\Microsoft-Windows-LanguageFeatures-TextToSpeech-en-gb-Package~31bf3856ad364e35~amd64~~.cab /PackagePath:.\Microsoft-Windows-LanguageFeatures-Speech-en-gb-Package~31bf3856ad364e35~amd64~~.cab

Edited June 20, 2019 by MartinByard

[lafleur1977]

Thanks for that, I will give that a try although I am just wondering if its easier to switch to english version...

[lafleur1977]

The DISM step(s) are specifically:

Dism /Online /Add-Package /PackagePath=".\Microsoft-Windows-Client-Language-Pack_x64_en-gb.cab"

 

I have downloaded the language pack & features on demand. I got all the files you mentioned from features on demand but I can't find the one for the language pack with the same name. There is a en-gb folder and inside it has lp.cab - is that the same file?

 

Thanks

[MartinByard]

I think so, yeah. I can't find the bookmark I used at the minute to work out how / why mine might be named differently. If need be I can throw what I've got up on the web and make it available for you.

[lafleur1977]

The language pack I got off VLSC was dated July 2015 which i thought was a bit odd, however the features on demand where dated nov 2018.

 

I have added them as applications in MDT now but they seem to be hanging on installation. Is there a certain time in the imaging process they should install maybe?

 

Thanks

[Valentine]

I had this issue with MDT and couldn't get it to work during the task sequence. In the end i just added them directly to the image file, I can probably dig up the exact commands if that's useful?

[MartinByard]

I've added the steps after it installs and configures the SCCM client, so that it runs whilst booted into Windows and not in WinPE ...

 

Edited June 21, 2019 by MartinByard

[lafleur1977]

I had this issue with MDT and couldn't get it to work during the task sequence. In the end i just added them directly to the image file, I can probably dig up the exact commands if that's useful?

 

Thanks, yes I will have a look at those if you are able to find them.

[lafleur1977]

I've added the steps after it installs and configures the SCCM client, so that it runs whilst booted into Windows and not in WinPE ...

 

[ATTACH=CONFIG]53946[/ATTACH]

 

Yes, that sounds about the same stage as where I have it. I will have a play around and see what I can work out. I noticed you have an option to enable .net 3.5 - would you mind telling me how you did that?

 

Thanks

[Mujja]

Thanks for that, I will give that a try although I am just wondering if its easier to switch to english version...

 

Like you say, easier to switch to a EN-INTL ISO.

[Valentine]

Thanks, yes I will have a look at those if you are able to find them.

 

I have left my server paths in as it's just easier to read. I have the ISO mounted on z:\ and the install.wim and temp locations should be changed as needed.

 

Dism /Mount-Image /ImageFile:"E:\DeploymentShare\Operating Systems\Windows 10 1809\sources\install.wim" /Name:"Windows 10 Education" /MountDir:e:\temp\image

Dism /Image:e:\temp\image /Add-Package /PackagePath:Z:\Microsoft-Windows-LanguageFeatures-Basic-en-gb-Package~31bf3856ad364e35~amd64~~.cab /PackagePath:Z:\Microsoft-Windows-LanguageFeatures-Handwriting-en-gb-Package~31bf3856ad364e35~amd64~~.cab /PackagePath:Z:\Microsoft-Windows-LanguageFeatures-OCR-en-gb-Package~31bf3856ad364e35~amd64~~.cab /PackagePath:Z:\Microsoft-Windows-LanguageFeatures-Speech-en-gb-Package~31bf3856ad364e35~amd64~~.cab /PackagePath:Z:\Microsoft-Windows-LanguageFeatures-TextToSpeech-en-gb-Package~31bf3856ad364e35~amd64~~.cab

Dism /Unmount-Image /MountDir:e:\temp\image /Commit

[MartinByard]

I did that in a similar method to adding the langugage features - got the .cab file from the features iso, added it to a package in sccm and ran a bit of powershell to add it :

# Specify location where the script is running from
$currentLocation = Split-Path -Parent $MyInvocation.MyCommand.Path;
# enable the feature, using the source files in the current folder, not running away to MS update
Enable-WindowsOptionalFeature -Online -FeatureName NetFx3 -Source $currentLocation -LimitAccess -All

[lafleur1977]

Thanks everyone for your help, I will give them a go

[lafleur1977]

I resolved the UAC prompt that I was originally having and I thought I'd share. I didn't need to install the language packs/features in the end although I did learn alot about that which was very useful. After I had trouble trying to add the features and language packs, I checked around in settings/control panel and could see english uk versions for language packs, features, but I could also see some english US versions trying to install and some english US options selected - the date was in american format for example.

 

I went back to where I set the language settings in the customsettings.ini/rules and added 2 more:

 

SystemLocale=en-GB

UserLocale=en-GB

 

I had actually removed these earlier on as I was automating the settings in the initial MDT deployment window, and those 2 settings didn't seem to populate an option. As soon as I added them back in, all the american stuff disappeared and only english UK settings where available in settings/control panel. The UAC prompt for standard users was resolved too.

 

Hopefully that makes sense and helps anyone else in a similar position.

 

Thanks for all your help

[lafleur1977]

I did that in a similar method to adding the langugage features - got the .cab file from the features iso, added it to a package in sccm and ran a bit of powershell to add it :

# Specify location where the script is running from
$currentLocation = Split-Path -Parent $MyInvocation.MyCommand.Path;
# enable the feature, using the source files in the current folder, not running away to MS update
Enable-WindowsOptionalFeature -Online -FeatureName NetFx3 -Source $currentLocation -LimitAccess -All

 

Thanks for this - I've now got NetFx3 installing as part of my deployment. I did it slightly differently, extracted the cab files from the features iso, and added them as a package in MDT. I didn't need to use the powershell as the task sequence included a step to apply packages uploaded to the MDT server.

 

Thanks for all your help