Since 26H2 will be 24H2 that is total shit what are you guys gonna do? Stay 23H2 or update unstable 24H2. You have to quite often press control + alt + del even get password box visible in lockscreen.. like what the fuck even basic shit doesn’t work. So not sure if we can stay on ”supported” version of windows and I wouldn’t say that 24H2 even have support if anything doesn’t work. So does it really matter if we stay 23H2. Our service desk just don’t have enough capacity so we cannot answer like 100 calls for day because login screen doesn’t work #Microslop

Hey all, hoping someone has run into this before.

System: Windows 11 25H2, build 26200.8117

The problem: Every other security update installs and downloads fine, but this one specific update won't go through:

• 2026-06 Preview Update (KB5095093) → target build 26200.8737
• Installation error: 0x80070032

What I've already tried:

• sfc /scannow completes, no fix
• Deleted the contents of C:\Windows\SoftwareDistribution
• Confirmed the Windows Update service is running
• Checked Group Policy (gpedit.msc), nothing blocking updates there
• Downloaded the update manually from the Microsoft Update Catalog, the installer runs but never finishes/fails to complete

DISM issue on top of it:

Since I suspected component store corruption, I tried:

DISM /Online /Cleanup-Image /RestoreHealth

This also fails, with error 0x800f0915, so I can't even repair the image to rule that out.

At this point I'm out of ideas. Has anyone dealt with this specific combo of 0x80070032 + 0x800f0915 on 25H2? Any other logs I should be pulling (CBS.log, DISM.log) or steps I'm missing?

tia!

https://preview.redd.it/cb926xr33vah1.png?width=475&format=png&auto=webp&s=1797ec5c8bf067a46ca23deff8c6fa0eca28065b

https://preview.redd.it/21n4zvx63vah1.png?width=429&format=png&auto=webp&s=f624422d3f352ccd5f5cf8e578939e93193b56e6

Hi all,

I'm running ConfigMgr Current Branch 2509 with Hotfix Rollup KB37864969 and am seeing what appears to be a site-wide application deployment reporting issue. Initially I thought this was a PatchMyPC or Client side deployment problem, but after digging into it for several hours the evidence points elsewhere.

The error being reported is:

0x87D00314 (-2016410860) CI Version Info timed out

I currently have:

ErrorCode      Records
------------   -------
-2016410860    13,784

This affects dozens of unrelated application deployments. For example:

AssignmentID   Records
------------   -------
16793680       409
16793921       409
16793667       407
16793620       406
16792258       406
16793616       406
...
16794003       361

The deployment I was investigating is a PatchMyPC Application, Microsoft Remote Help 5.2.1037.0. Client-side everything appears healthy with expected values in AppIntentEval.log, CCM_Application WMI and StateMessage.log.

The strange part is what I see when joining deployment asset details and deployment error details in SQL I get conflicting information.

MachineName      ComplianceState  EnforcementState  InstalledState  ErrorCode
--------------   ---------------  ----------------  --------------  ---------
LAPTOP01         1                1000              2               -2016410860
LAPTOP02         1                1000              2               -2016410860
LAPTOP03         1                1000              2               -2016410860
LAPTOP04         1                1000              2               -2016410860

Even stranger, the Application CI summary disagrees with the error view. For Remote Help I have 378 successful installs in the Application CI summary. However vAppDeploymentErrorAssetDetails contains 361 rows for the same deployment. The error records themselves don't contain much useful information. Most of the records are:

ExtendedInfoID = 0
ExtendedInfoDescriptionID = 0

New deployments show the same behaviour.

At this point it feels like SCCM is simultaneously recording success and failure for the same deployment instance. Any ideas appreciated.

Hello everyone,

I'm wondering if things have changed regarding on how to size SQL Database, number of files to create and such. My SCCM installation is quite old and sometime, we do stuff that aren't needed anymore.

Currently, it's on a Virtual Server that have 8 cpu and 64GB ram. The SCCM Database Files are 8 files of 60GB each with about 50% free space in each, all on the same drive. The log file is on another drive at 50GB (will be raised to a 100gb disk today since it's getting full).I'm pretty sure all drive are linked to the same NAS in the backend.

SQL is set to use about 80% of the ram (around 50gb).

I'm wondering if creating 8 files because of 8 virtual core is still the way to go and if I should downsize my files.

Thank you

There is an OSD issue with DCU 5.6-5.7.
Dell posted this on their website and said an update (5.7.1) would be out end of June. So far no update. Any one know when this fixed version will be released?

I'm using Invoke-ADTAllUsersRegistryAction with -ScriptBlock {} to set registry keys in user hives for the install part. All good, works as intended.

I want to reverse the changes in the uninstall part.

So my thinking is I repeat the same process, where keys are removed (not set in anyway), using Remove-ADTRegistryKey this should be OK I assume? Silly question, as the Default hive is also modified, it's only going to remove the keys from the Default hive once, right?

It's not going to continually remove the keys from any new user logins after the application has been uninstalled?

TLDR: Reg keys in the Default hive are copied to new logins. If a key doesn't exist in the Default hive, it's not going to remove it on any new logins... right?

Has anyone experienced an application, specifically, that when installing, it displays a popup and no matter what you do to try stop it, nothing works.

There is this application I am wanting to install via sccm called DjVu Web Browser Plugin. - it's an MSI.
At the end of the installation, this popup shows and you have to click OK or at least close the box for the install to complete otherwise it just hangs.

https://preview.redd.it/yr66qzbvghah1.png?width=2313&format=png&auto=webp&s=46f2acf147e282aad3b48b966045b06ed9af922c

Here is my original script - which doesn't stop the popup.

$scriptPath = $MyInvocation.MyCommand.Path
$dir = Split-Path $scriptPath


$msi = Join-Path $dir 'DjVu_Plugin.msi'
$log = Join-Path $env:TEMP 'DjVu_MSI.log'


Start-Process "msiexec.exe" -ArgumentList "/i `"$msi`" /qn REBOOT=ReallySuppress /l*v `"$log`"" -NoNewWindow
   


Write-Host "MSI log: $log"

I then tried PSADT - which the below script works when run manually as system context in powershell on a computer but when run via sccm, the install just hangs. Now, as you see above in my screenshot, you can see the child msi process with the main window title "DjVu Installation" - that's what happens when running this script manually but when running via sccm, it creates the child process but with no "window title" name and I believe it's because SCCM can't actually see the popup, therefore the below script won't work.

I have also tried an MSI editor but for the life of me, I cannot figure out what part of the MSI is causing the popup. Also tried creating an MST but again, I don't really know what part of the MSI is causing it.

<#


.SYNOPSIS
PSAppDeployToolkit - This script performs the installation or uninstallation of an application(s).


.DESCRIPTION
- The script is provided as a template to perform an install, uninstall, or repair of an application(s).
- The script either performs an "Install", "Uninstall", or "Repair" deployment type.
- The install deployment type is broken down into 3 main sections/phases: Pre-Install, Install, and Post-Install.


The script imports the PSAppDeployToolkit module which contains the logic and functions required to install or uninstall an application.


.PARAMETER DeploymentType
The type of deployment to perform.


.PARAMETER DeployMode
Specifies whether the installation should be run in Interactive (shows dialogs), Silent (no dialogs), NonInteractive (dialogs without prompts) mode, or Auto (shows dialogs if a user is logged on, device is not in the OOBE, and there's no running apps to close).


Silent mode is automatically set if it is detected that the process is not user interactive, no users are logged on, the device is in Autopilot mode, or there's specified processes to close that are currently running.


.PARAMETER SuppressRebootPassThru
Suppresses the 3010 return code (requires restart) from being passed back to the parent process (e.g. SCCM) if detected from an installation. If 3010 is passed back to SCCM, a reboot prompt will be triggered.


.PARAMETER TerminalServerMode
Changes to "user install mode" and back to "user execute mode" for installing/uninstalling applications for Remote Desktop Session Hosts/Citrix servers.


.PARAMETER DisableLogging
Disables logging to file for the script.


.EXAMPLE
powershell.exe -File Invoke-AppDeployToolkit.ps1


.EXAMPLE
powershell.exe -File Invoke-AppDeployToolkit.ps1 -DeployMode Silent


.EXAMPLE
powershell.exe -File Invoke-AppDeployToolkit.ps1 -DeploymentType Uninstall


.EXAMPLE
Invoke-AppDeployToolkit.exe -DeploymentType Install -DeployMode Silent


.INPUTS
None. You cannot pipe objects to this script.


.OUTPUTS
None. This script does not generate any output.


.NOTES
Toolkit Exit Code Ranges:
- 60000 - 68999: Reserved for built-in exit codes in Invoke-AppDeployToolkit.ps1, and Invoke-AppDeployToolkit.exe
- 69000 - 69999: Recommended for user customized exit codes in Invoke-AppDeployToolkit.ps1
- 70000 - 79999: Recommended for user customized exit codes in PSAppDeployToolkit.Extensions module.


.LINK
https://psappdeploytoolkit.com


#>


[CmdletBinding()]
param
(
    # Default is 'Install'.
    [Parameter(Mandatory = $false)]
    [ValidateSet('Install', 'Uninstall', 'Repair')]
    [System.String]$DeploymentType,


    # Default is 'Auto'. Don't hard-code this unless required.
    [Parameter(Mandatory = $false)]
    [ValidateSet('Auto', 'Interactive', 'NonInteractive', 'Silent')]
    [System.String]$DeployMode,


    [Parameter(Mandatory = $false)]
    [System.Management.Automation.SwitchParameter]$SuppressRebootPassThru,


    [Parameter(Mandatory = $false)]
    [System.Management.Automation.SwitchParameter]$TerminalServerMode,


    [Parameter(Mandatory = $false)]
    [System.Management.Automation.SwitchParameter]$DisableLogging
)



##================================================
## MARK: Variables
##================================================


# Zero-Config MSI support is provided when "AppName" is null or empty.
# By setting the "AppName" property, Zero-Config MSI will be disabled.
$adtSession = @{
    # App variables.
    AppVendor = 'DjVu'
    AppName = 'DjVu'
    AppVersion = '8.2.160.0'
    AppArch = '32bit'
    AppLang = 'EN'
    AppRevision = '01'
    AppSuccessExitCodes = @(0)
    AppRebootExitCodes = @(1641, 3010)
    AppProcessesToClose = @()  # Example: @('excel', @{ Name = 'winword'; Description = 'Microsoft Word' })
    AppScriptVersion = '1.0.0'
    AppScriptDate = (Get-Date -Format yyyy-MM-dd)
    AppScriptAuthor = ''
    RequireAdmin = $false


    # Install Titles (Only set here to override defaults set by the toolkit).
    InstallName = ''
    InstallTitle = ''


    # Script variables.
    DeployAppScriptFriendlyName = $MyInvocation.MyCommand.Name
    DeployAppScriptParameters = $PSBoundParameters
    DeployAppScriptVersion = '4.1.8'
}


function Install-ADTDeployment
{
    [CmdletBinding()]
    param
    (
    )


    ##================================================
    ## MARK: Pre-Install
    ##================================================
   <# 
   $adtSession.InstallPhase = "Pre-$($adtSession.DeploymentType)"


    ## Show Welcome Message, close processes if specified, allow up to 3 deferrals, verify there is enough disk space to complete the install, and persist the prompt.
    $saiwParams = @{
       AllowDefer = $true
        DeferTimes = 3
        CheckDiskSpace = $true
        PersistPrompt = $true
    }
    if ($adtSession.AppProcessesToClose.Count -gt 0)
    {
        $saiwParams.Add('CloseProcesses', $adtSession.AppProcessesToClose)
    }
    Show-ADTInstallationWelcome 


    ## Show Progress Message (with the default message).
    #Show-ADTInstallationProgress
    #>


    ## <Perform Pre-Installation tasks here>
    


    ##================================================
    ## MARK: Install
    ##================================================
    $adtSession.InstallPhase = $adtSession.DeploymentType


    ## Handle Zero-Config MSI installations.
    if ($adtSession.UseDefaultMsi)
    {
        $ExecuteDefaultMSISplat = @{ Action = $adtSession.DeploymentType; FilePath = $adtSession.DefaultMsiFile }
        if ($adtSession.DefaultMstFile)
        {
            $ExecuteDefaultMSISplat.Add('Transforms', $adtSession.DefaultMstFile)
        }
        Start-ADTMsiProcess at
        if ($adtSession.DefaultMspFiles)
        {
            $adtSession.DefaultMspFiles | Start-ADTMsiProcess -Action Patch
        }
    }


    ## <Perform Installation tasks here>
    $PopupKiller = Start-Job -ScriptBlock {


    while ($true)
    {
        $process = Get-Process msiexec -ErrorAction SilentlyContinue |
            Where-Object { $_.MainWindowTitle -eq 'DjVu Installation' }


        if ($process)
        {
            $process | Stop-Process -Force
            break
        }


        Start-Sleep -Milliseconds 500
    }
}


Start-ADTMsiProcess `
    -Action Install `
    -FilePath "$PSScriptRoot\Files\DjVu_Plugin.msi" `
    -ArgumentList "/qn"


Remove-Job $PopupKiller -Force -ErrorAction SilentlyContinue









    ##================================================
    ## MARK: Post-Install
    ##================================================
  
    $adtSession.InstallPhase = "Post-$($adtSession.DeploymentType)"


    ## <Perform Post-Installation tasks here>



    ## Display a message at the end of the install.
    if (!$adtSession.UseDefaultMsi)
    {
        Show-ADTInstallationPrompt -Message 'DjVu install 99% completed, please restart your computer to complete installation.' -ButtonRightText 'OK' -NoWait
    }
}




function Uninstall-ADTDeployment
{
    [CmdletBinding()]
    param
    (
    )


    ##================================================
    ## MARK: Pre-Uninstall
    ##================================================
    $adtSession.InstallPhase = "Pre-$($adtSession.DeploymentType)"


    ## If there are processes to close, show Welcome Message with a 60 second countdown before automatically closing.
    if ($adtSession.AppProcessesToClose.Count -gt 0)
    {
        Show-ADTInstallationWelcome -CloseProcesses $adtSession.AppProcessesToClose -CloseProcessesCountdown 60
    }


    ## Show Progress Message (with the default message).
    Show-ADTInstallationProgress


    ## <Perform Pre-Uninstallation tasks here>



    ##================================================
    ## MARK: Uninstall
    ##================================================
    $adtSession.InstallPhase = $adtSession.DeploymentType


    ## Handle Zero-Config MSI uninstallations.
    if ($adtSession.UseDefaultMsi)
    {
        $ExecuteDefaultMSISplat = @{ Action = $adtSession.DeploymentType; FilePath = $adtSession.DefaultMsiFile }
        if ($adtSession.DefaultMstFile)
        {
            $ExecuteDefaultMSISplat.Add('Transforms', $adtSession.DefaultMstFile)
        }
        Start-ADTMsiProcess at
    }


    ## <Perform Uninstallation tasks here>



    ##================================================
    ## MARK: Post-Uninstallation
    ##================================================
    $adtSession.InstallPhase = "Post-$($adtSession.DeploymentType)"


    ## <Perform Post-Uninstallation tasks here>
}


function Repair-ADTDeployment
{
    [CmdletBinding()]
    param
    (
    )


    ##================================================
    ## MARK: Pre-Repair
    ##================================================
    $adtSession.InstallPhase = "Pre-$($adtSession.DeploymentType)"


    ## If there are processes to close, show Welcome Message with a 60 second countdown before automatically closing.
    if ($adtSession.AppProcessesToClose.Count -gt 0)
    {
        Show-ADTInstallationWelcome -CloseProcesses $adtSession.AppProcessesToClose -CloseProcessesCountdown 60
    }


    ## Show Progress Message (with the default message).
    Show-ADTInstallationProgress


    ## <Perform Pre-Repair tasks here>



    ##================================================
    ## MARK: Repair
    ##================================================
    $adtSession.InstallPhase = $adtSession.DeploymentType


    ## Handle Zero-Config MSI repairs.
    if ($adtSession.UseDefaultMsi)
    {
        $ExecuteDefaultMSISplat = @{ Action = $adtSession.DeploymentType; FilePath = $adtSession.DefaultMsiFile }
        if ($adtSession.DefaultMstFile)
        {
            $ExecuteDefaultMSISplat.Add('Transforms', $adtSession.DefaultMstFile)
        }
        Start-ADTMsiProcess at
    }


    ## <Perform Repair tasks here>



    ##================================================
    ## MARK: Post-Repair
    ##================================================
    $adtSession.InstallPhase = "Post-$($adtSession.DeploymentType)"


    ## <Perform Post-Repair tasks here>
}



##================================================
## MARK: Initialization
##================================================


# Set strict error handling across entire operation.
$ErrorActionPreference = [System.Management.Automation.ActionPreference]::Stop
$ProgressPreference = [System.Management.Automation.ActionPreference]::SilentlyContinue
Set-StrictMode -Version 1


# Import the module and instantiate a new session.
try
{
    # Import the module locally if available, otherwise try to find it from PSModulePath.
    if (Test-Path -LiteralPath "$PSScriptRoot\PSAppDeployToolkit\PSAppDeployToolkit.psd1" -PathType Leaf)
    {
        Get-ChildItem -LiteralPath "$PSScriptRoot\PSAppDeployToolkit" -Recurse -File | Unblock-File -ErrorAction Ignore
        Import-Module -FullyQualifiedName @{ ModuleName = "$PSScriptRoot\PSAppDeployToolkit\PSAppDeployToolkit.psd1"; Guid = '8c3c366b-8606-4576-9f2d-4051144f7ca2'; ModuleVersion = '4.1.8' } -Force
    }
    else
    {
        Import-Module -FullyQualifiedName @{ ModuleName = 'PSAppDeployToolkit'; Guid = '8c3c366b-8606-4576-9f2d-4051144f7ca2'; ModuleVersion = '4.1.8' } -Force
    }


    # Open a new deployment session, replacing $adtSession with a DeploymentSession.
    $iadtParams = Get-ADTBoundParametersAndDefaultValues -Invocation $MyInvocation
    $adtSession = Remove-ADTHashtableNullOrEmptyValues -Hashtable $adtSession
    $adtSession = Open-ADTSession  u/iadtParams -PassThru
}
catch
{
    $Host.UI.WriteErrorLine((Out-String -InputObject $_ -Width ([System.Int32]::MaxValue)))
    exit 60008
}



##================================================
## MARK: Invocation
##================================================


# Commence the actual deployment operation.
try
{
    # Import any found extensions before proceeding with the deployment.
    Get-ChildItem -LiteralPath $PSScriptRoot -Directory | & {
        process
        {
            if ($_.Name -match 'PSAppDeployToolkit\..+$')
            {
                Get-ChildItem -LiteralPath $_.FullName -Recurse -File | Unblock-File -ErrorAction Ignore
                Import-Module -Name $_.FullName -Force
            }
        }
    }


    # Invoke the deployment and close out the session.
    & "$($adtSession.DeploymentType)-ADTDeployment"
    Close-ADTSession
}
catch
{
    # An unhandled error has been caught.
    $mainErrorMessage = "An unhandled error within [$($MyInvocation.MyCommand.Name)] has occurred.`n$(Resolve-ADTErrorRecord -ErrorRecord $_)"
    Write-ADTLogEntry -Message $mainErrorMessage -Severity 3


    ## Error details hidden from the user by default. Show a simple dialog with full stack trace:
    # Show-ADTDialogBox -Text $mainErrorMessage -Icon Stop -NoWait


    ## Or, a themed dialog with basic error message:
    # Show-ADTInstallationPrompt -Message "$($adtSession.DeploymentType) failed at line $($_.InvocationInfo.ScriptLineNumber), char $($_.InvocationInfo.OffsetInLine):`n$($_.InvocationInfo.Line.Trim())`n`nMessage:`n$($_.Exception.Message)" -ButtonRightText OK -Icon Error -NoWait


    Close-ADTSession -ExitCode 60001
}

I'm looking into Patch My PC and was hoping I could get some details on why people find it better than free alternatives (Action1, Ninite, etc.). How does PMPC get data/perform software inventory? Likes and dislikes? Any other thoughts please let me know.

Edit: appreciate the input everyone!

Hi, because this months w11 25h2 cumulative update KB5094126 contains this known issue: " certain third-party applications might be unable to launch Microsoft Office applications ", I need to uninstall that cumulative update from several hundred computers.

I think one should uninstall updates these days using dism command, no more using wusa command.

So, my problem is that I can find out package name using this command:

dism /online /get-packages

and I know that uninstall command is for this months cumulative update is:

dism /Online /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.8655.1.20

but my problem is that computer needs to restart after running that dism command.

So, how do I tell sccm to wait until running that dism command is finished before restarting computer? Thanks in advance if anybody can help.

Since I’ve come across conflicting information, I’m asking the question here:

I want to replace my existing passive site (which has the SMS Provider installed) with a new passive site.

Question 1)
When uninstalling the passive site, is the SMS Provider role automatically uninstalled as well?

Question 2)
When installing the new passive site, is the SMS Provider role automatically installed as well?

As I understand it: for Question 1, the answer is no—I have to uninstall the role manually; and for Question 2, the answer is also no—I have to manually install the role afterwards.

Can anyone confirm this (based on personal experience)?

Hi All,

we currently just use a Win11 boot disk (usb) to decom old machines before we sell them, this is fine, but we have a larger number coming up and was hoping to use sccm to make it just a bit easier to do more than one at a time.

I've had a bit of a search and some people have had similar disussions on here and other forums, but nothing seems to work for me, or I may be just missing something.

I've created a TS that:
Boots to PE
Partitions the disk (uefi)
applies the OS (just an extracted Os source)
apply device drivers
Restarts and boots to the new OS.

This works to a point, but when the machine boots after completing the TS, it's at the login screen but as the admin creds are randomised, and it doesn't run OOBE it's pretty useless.

has anyone any suggestions on doing this in a more succesful way?

we just want to wipe it, apply OS, and for the machine to run OOBE (as you would on first boot if applying the OS from a win11 bootable disk/usb). so that we can hand it to someone and when they turn it on they get the usual vanilla setup.

any help appreciated.

I have tried.

1. Deleting the deployment, making a copy of the deployment and deploying that

2. Re-installing the sccm client

3. Deleting SCCM cache

4. Rebooting endpoints

Still 10 endpoints stuck on Program received.

I'm getting a screen that says why did my pc restart? after updating my task sequence with this months iso. it looks like it might not be recognizing the ethernet connection at first. if i click next, it boots correctly.

Our environment is co-managed. We have the slider set to manage Windows updates to intune. We also have patch my PC and the publisher install locally on the server. We’re finding now that Windows updates are blocked with this configuration unless we turn software updates to no in the client settings, however for patch my PC that is a requirement to have that turned on. We’re pretty new to patch my PC.

Any tips? For giggles we turned off software updates and then patches seem to come in.