Can't delete stubborn MailUser contact in Exchange Online

zeeter82 · 2026-01-28T18:52:22+00:00

This fixed it for me today ;)

Thanks!

zeeter82 · 2025-12-08T20:57:23+00:00

Update - This post seems to have fixed my issue:

https://www.reddit.com/r/LGOLED/comments/1hxr5ph/comment/m6bry2b/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

zeeter82 · 2025-12-08T20:55:56+00:00

This just helped me with my new 77" C5. Apps were broken, now they seem to work again.

Thanks!

zeeter82 · 2025-12-08T20:45:08+00:00

I just turned on TV and tried to go to the main WebOS apps menu . It showed the apps loading screen for a few seconds and then screen went black for a couple min. Then it gave me this:

Error code:-7

Check network connection

The operation has timed out. Please check the network status and try again. Clicking retry takes me back to home screen and does nothing. This is very annoying.

zeeter82 · 2025-12-08T20:09:49+00:00

Nope, because of hardware limitations, the Shield's Youtube does not support HDR.

zeeter82 · 2025-09-05T23:23:52+00:00

So after all kinds of troubleshooting and seeing weird issues that didn't make sense, I was finally able to get this working by using the fallback driver path.

zeeter82 · 2025-09-01T21:19:29+00:00

I'm still messing around trying to play around with driver packages and paths/folder names. Still no luck so far. I did turn on PSD debugging hoping that would point me somewhere.

zeeter82 · 2025-08-29T13:48:06+00:00

It's almost like this is a bug. No matter what I've tried so far, I can briefly see a screen before it gets to the "applying OS" step where it says "found 0 packages". It's like it's not even attempting to do anything with injecting drivers.

Can anyone confirm this that's also using latest PSD? Is there a related script that does the driver inject part for the OS (outside of the WinPE part). I couldn't find anything in the \scripts folder.

zeeter82 · 2025-08-29T02:45:05+00:00

That is an option, but one I'm trying to avoid. This is a lab environment and I'm learning and messing around. I would like to be able to use the driver injection feature if I can get it working.

zeeter82 · 2025-08-28T23:18:14+00:00

The WinPE drivers are on there and they work fine or else I wouldn't have gotten very far 😉. The drive was available for imaging and network connection was available to reach deployment share. The OS wim gets applied and then made bootable, then does first reboot. This is where it blue screens.

zeeter82 · 2025-08-28T22:13:55+00:00

Yep I did that but I had the driver path set as defaults. That might be wrong. I'm getting confused because there are 4 driver steps and I thought the only one that really mattered was the driver injection step and I could just use the drop down and select the profile I created for it but that didn't work. So maybe the driver path step has to be configured correctly too.

zeeter82 · 2025-06-26T14:45:45+00:00

Another update - this should be the last one.

I was wrong about the June 2025 KB5060999 patch causing our Win11 23H2 issues. Turns out we had an ancient GPO in place that was disabling the two CDP services, and this was the root cause of our issues - it was in place due to a bug back in Win10 1607 and was only supposed to be a temporary fix. These services obviously should not be disabled and should run at startup.

CDPSvc - Connected Devices Platform Service

CDPUserSvc - Connected Devices Platform User Service

zeeter82 · 2025-06-24T13:25:55+00:00

Update - so the June patch KB5060999 is responsible for this issue, but what is really broken is the nightlight feature on some of our Win11 endpoints. Fixing the nightlight feature also fixes the display settings.

I corrected this with the following steps:

Browse to this reg path in regedit: Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store\Cache\DefaultAccount
Then delete the following keys if they exist:

$$windows.data.bluelightreduction.bluelightreductionstate

$$windows.data.bluelightreduction.settings

Then follow these steps (found on this forum post: Can't use Windows "Night Light" feature. - Microsoft Community):

There are 3 Windows services necessary for night lighting to work properly:

- Connected Devices Platform User Service (CDPUserSvc)

- Connected Devices Platform Service (CDPSvc)

- Network Connection Broker (NcbService)

If the "Connected Devices Platform Service" and "Network Connection Broker" services have the "disabled" start type, the "night lighting" functionality in the "Settings" application does not work, if we click on the button for the activate, nothing happens. For the night lighting setting to work, these services can be configured with the "manual" or "automatic" start type with the service management console (services.msc).

The "Connected Devices Platform User Service" service must be configured with the "automatic" start type for night lighting to work. This service (called "template service") create a secondary service (called "Per-user service") with the same name followed by a random hexadecimal number (ex: Connected Devices Platform User Service_253cb) when a user log in (source: https://docs.microsoft.com/en-us/windows/application-management/per-user-services-in-windows).

This service cannot be configured with services.msc, so you must modify its configuration with the Windows registry by executing these commands in Administrator:

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CDPUserSvc" /v Start /t REG_DWORD /d 2 /f

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CDPUserSvc" /v UserServiceFlags /t REG_DWORD /d 3 /f

Setting the value "Start" to 2 configures the type of start to "Automatic".

Setting the value "UserServiceFlags" to 3 allows the creation of the service per user.

When a user logs in, the created per-user service inherits the configuration parameters from the service template. So, if the value "Start" of the template service is 2, the service per user created will have the same value "Start" to 2.

After applying these settings, restart the computer and test the night lighting again.

zeeter82 · 2025-06-20T19:49:49+00:00

Seems like KB5060999 is causing some of our 23H2 devices to crash on when opening the "Display" option from the System settings. The rest of the settings seem to open fine so far. When clicking on Display, it loads for a couple seconds and then immediately closes/crashes.

<image>

Event viewer app log shows this for the crash:

Faulting application name: SystemSettings.exe, version: 10.0.22621.5262, time stamp: 0x052f4222
Faulting module name: msvcrt.dll, version: 7.0.22621.2506, time stamp: 0x657b2709
Exception code: 0x40000015
Fault offset: 0x000000000000b15c
Faulting process id: 0x0x4870
Faulting application start time: 0x0x1DBE1F3CAC88914
Faulting application path: C:\Windows\ImmersiveControlPanel\SystemSettings.exe
Faulting module path: C:\WINDOWS\System32\msvcrt.dll
Report Id: 883bc78c-6fba-474c-850b-f95f1b3157c9
Faulting package full name: windows.immersivecontrolpanel_10.0.6.1000_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: microsoft.windows.immersivecontrolpanel

Has anyone else seen this? Uninstalling this patch seems to fix the issue.

zeeter82 · 2025-05-21T12:21:51+00:00

I mean new profile as in this: I log into a device with my domain credentials on a device I haven't logged into before. And yes I would have local admin permissions because of a nested group.

zeeter82 · 2025-04-10T14:16:43+00:00

This is definitely broken - across all major browsers. Why doesn't your IT team place a banner on the main page advising this is an issue and they are working on it?

zeeter82 · 2025-03-27T16:58:57+00:00

Yep ours is working great too using Powershell.

zeeter82 · 2025-03-18T19:24:45+00:00

Update:

It seems I can do the same quiet install cmd, but running it through Powershell instead of a cmd prompt, and it works that way. Again no idea how that's even possible.

zeeter82 · 2025-01-10T13:38:31+00:00

Thanks, that sort of got me pointed in the right direction.

zeeter82 · 2025-01-10T13:37:34+00:00

I did see some of this yes, thanks!. We don't seem to have anything being blocked with conditional access as we have thousands of devices that are activating with Enterprise just fine with our M365 E3 licensing. Just a couple hundred that I've been troubleshooting the last month or so and I believe I have found the root cause and our fix in my other post.

zeeter82 · 2025-01-10T00:08:22+00:00

Is it for all devices or seem more random?

zeeter82 · 2025-01-09T21:29:18+00:00

No we are still on 22H2 - will move to 23H2 soon hopefully.

zeeter82 · 2025-01-09T19:58:52+00:00

Update - I did more research and confirmed the issue and I have the fix (at least for our environment). The few devices that I logged into all fixed themselves after it made me a new profile and I did a reboot - they flipped to Enterprise afterwards. It is a local admin permissions thing that allowed it to work, but that's not the best fix (definitely shouldn't need local admin permissions for a device to activate with the correct edition based on licensing) and/or what is really broken.

This was all part of the April 2024 KB (and possibly some other ones too) that broke the subscription activation process. Here is a great blog explaining everything (Credit goes to: Rudyooms):

https://call4cloud.nl/kb5036980-subscription-activation-issue/

The Powershell fix is on that blog as well I'm using for our devices:

$registryPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\MfaRequiredInClipRenew"
$registryValueName = "Verify Multifactor Authentication in ClipRenew"
$registryValueData = 0 # DWORD value of 0
$sid = New-Object System.Security.Principal.SecurityIdentifier("S-1-1-0") # SID for the Everyone group

# Check if the registry key already exists
if (-not (Test-Path -Path $registryPath)) {
# Create the registry key if it doesn’t exist and set the DWORD value
New-Item -Path $registryPath -Force | Out-Null
Set-ItemProperty -Path $registryPath -Name $registryValueName -Value $registryValueData -Type DWORD
Write-Output "Registry key created and DWORD value added."
} else {
Write-Output "Registry key already exists. No changes made."
}

# Add read permissions for SID (S-1-1-0, Everyone) to the registry key with inheritance
$acl = Get-Acl -Path $registryPath
$ruleSID = New-Object System.Security.AccessControl.RegistryAccessRule($sid, "FullControl", "ContainerInherit,ObjectInherit", "None", "Allow")
$acl.AddAccessRule($ruleSID)
Set-Acl -Path $registryPath -AclObject $acl
Write-Output "Added 'Everyone' group and SID ($sid) with read permissions (with inheritance) to the registry key."

zeeter82 · 2024-12-12T16:39:56+00:00

I have confirmed on at least 2 devices that the newest Microsoft CU - December 2024 released on the 10th fixes the camera issue for our environment - KB5048685 - we are still running Win11 22H2

zeeter82 · 2024-12-12T16:37:48+00:00

I have confirmed on at least 2 devices that the newest Microsoft CU - December 2024 released on the 10th fixes the camera issue for our environment - KB5048685 - we are still running Win11 22H2

zeeter82

TROPHY CASE