AdamGrossTX/Windows10FeatureUpdates

Issues

• Setupdiag.exe does not exists

  #31 opened a year ago by KhalidIbrahimwork
  0

• Process-SetupDiag.ps1 tries to delete C:\Windows\System32 folder

  #29 opened 3 years ago by bachirica
  1

• NewDateTime variable output may vary depending on culture settings

  #27 opened 3 years ago by astratom
  0

• Process-SetupDiag.ps1 error

  #26 opened 3 years ago by clckr24
  0

• Handle Authenticated Users in multiple languages if possible

  #25 opened 3 years ago by tju-pwsh
  1

• Feature Request: Versioning for Application Detection Method

  #17 opened 4 years ago by Chadwicksracing
  2

• If the framework script has been run once and the application has been created, the script fails on the next run.

  #23 opened 4 years ago by AdamGrossTX
  1

• SetupDiag CI doesn't force SetupDiag to run in some cases

  #22 opened 4 years ago by AdamGrossTX
  1

• Authenticated Users have Modify permissions on ~FeatureUpdateTemp

  #19 opened 4 years ago by astratom
  1

• Feature Request: Language Packs

  #20 opened 4 years ago by boozeman
  1

• Computer\HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup\Tracking missing RollbackCount

  #18 opened 4 years ago by AdamGrossTX
  0

• Feature req: cleanup script post upgrade

  #16 opened 4 years ago by anjillan
  0

• Add support for checking if Compat Hard Blockers exist

  #15 opened 4 years ago by AdamGrossTX
  0

• Add support for Compat ScanOnly

  #14 opened 4 years ago by AdamGrossTX
  0

• Add support for duplicate entries in SetupConfig.ini

  #13 opened 4 years ago by AdamGrossTX
  0

• Add Support for Windows 10 2004 Options

  #12 opened 4 years ago by AdamGrossTX
  0

• Incorrect variable usage = blank display on write-host

  #9 opened 4 years ago by StevybSC
  0

• SetupDiag Inventory fails if no DateTime property exists

  #11 opened 4 years ago by AdamGrossTX
  0

• Compliance Item [Feature Update - SetupConfig.ini] fails compliance

  #10 opened 4 years ago by clckr24
  0

• Latest "bug fixes" (03/09/20) has broken a few things.

  #7 opened 4 years ago by StevybSC
  10

• Baseline [Feature Update - Scripts and Files Are Present] fails compliance

  #8 opened 4 years ago by StevybSC
  1

• [Parameter()] [string]$Path = "C:\~FeatureUpdateTemp",

  #3 opened 4 years ago by Chadwicksracing
  0

• [Parameter()] [string]$TranscriptPath = "%windir%\CCM\Logs\FeatureUpdate-CopyFiles.log",

  #4 opened 4 years ago by Chadwicksracing
  0

• [Parameter()] [string]$BaselineName = "Feature Update - Feature Update FIles"

  #5 opened 4 years ago by Chadwicksracing
  0

• . (Join-Path -Path $PSScriptRoot -ChildPath ".\Trigger-DCMEvaluation.ps1" -ErrorAction SilentlyContinue)

  #6 opened 4 years ago by Chadwicksracing
  0

• Type mismatch for property "InstallAttempts" in New-WMIRegistryClass-SetupDiag.ps1

  #2 opened 4 years ago by ladewig
  0

• Drivers line is incorrect

  #1 opened 5 years ago by HeyZeus-Tech
  1