![windows 10 aio v1607 windows 10 aio v1607](https://1.bp.blogspot.com/-5gxDN-jOsxo/XarZx3_d-FI/AAAAAAAAB9c/5y1ewSM2VmA6gT1uAYj3-ZZA6yDbfKxTQCEwYBhgL/s1600/s3.jpg)
I do that repair and after a reboot it shows in the start menu.
![windows 10 aio v1607 windows 10 aio v1607](https://149584678.v2.pressablecdn.com/wp-content/uploads/2021/03/Windows-10-versions-list.png)
After a computer is sysprep'd and imaged it does show as an installed program, and if you go to install it again it thinks its installed because it asks to do a repair on it. We have the same issue where Dell Command Update 3.0 will show installed but there isn't any way to launch it. Gets as close to an LTSC install as you can without really being Enterprise LTSC. we boot into audit mode and run this decrapifier power shell script to clean it up. When we get a new model PC for the first time, lets say an Optiplex 5060. Since this is a Windows 10 "app" I wonder if this script is buggering it up. Is anyone here using the Win10 decrapifier by CSAND?
#Windows 10 aio v1607 how to
Now it would be great if I didn't have to do Step 4 so if anyone has any ideas how to clean it up through the MDT process it would be appreciated. The Start Menu shortcut should be restored without requiring a reinstall. Step 4: Go to the Windows 10 "Apps & Features" settings, scroll down to "Dell Command | Update", click Advanced Options and then scroll down and click "Reset". Almost all of the time the program shortcut does not show up in the start menu, like a previous posted mentioned. Step 3: Run a computer through the MDT process and check that Command Update did get installed (we are using Windows 10 1809). Step 2: Copied that MSI to my deployment server and added a new MDT application and used the following install command "msiexec /i DellCommandUpdateApp.msi /passive /norestart" Mine was "C:\WINDOWS\\DellCommandUpdateApp.msi" In that log it should show the path to the MSI it extracted. Step 1: Installed Command Update on a regular Dell PC and then looked at the installation log file at the end of the installation wizard. I figured out the process to silently deploy version 3.0.1 with MDT and I'm posting it here in that it might help others out and maybe someone will have a solution for the one minor issue I have after it's installed.