none
MDT 2031 update 2 - Start screen and removing inbox apps don't work during in place upgrade RRS feed

  • Question

  • Hello

    I have upgraded my windows 10 to build 1703 and also installed adk 1703 on mdt server.

    start screen and remove inbox apps work fine during fresh install but don't work during in place upgrade.

    the TS log shows the xml file copied successfully, but when I check the location the file is not there:

    <![LOG[Start executing an instruction. Instruction name: start screen. Instruction pointer: 20]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="engine.cxx:140">
    <![LOG[Set a global environment variable _SMSTSCurrentActionName=start screen]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:662">
    <![LOG[Set a global environment variable _SMSTSNextInstructionPointer=20]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:662">
    <![LOG[Set a local default variable PackageID]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:694">
    <![LOG[Set a local default variable RunAsUser]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:694">
    <![LOG[Set a local default variable SMSTSRunCommandLineUserName]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:694">
    <![LOG[Set a local default variable SMSTSRunCommandLineUserPassword]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:694">
    <![LOG[Set a local default variable LoadProfile]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:694">
    <![LOG[Set a global environment variable _SMSTSLogPath=C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:662">
    <![LOG[Expand a string: Xcopy /e /s /y /h /i %scriptroot%\Custom_Script\win10\layoutmodification.xml %OSDISK%\users\Default\Appdata\local\microsoft\windows\Shell\]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:776">
    <![LOG[Expand a string: ]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:776">
    <![LOG[Start executing the command line: Xcopy /e /s /y /h /i %scriptroot%\Custom_Script\win10\layoutmodification.xml %OSDISK%\users\Default\Appdata\local\microsoft\windows\Shell\]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="instruction.cxx:731">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="instruction.cxx:760">
    <![LOG[Expand a string: WinPEandFullOS]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:776">
    <![LOG[Executing command line: Xcopy /e /s /y /h /i %scriptroot%\Custom_Script\win10\layoutmodification.xml %OSDISK%\users\Default\Appdata\local\microsoft\windows\Shell\]LOG]!><time="19:23:36.316+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="commandline.cpp:828">
    <![LOG[Process completed with exit code 0]LOG]!><time="19:23:36.832+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="commandline.cpp:1124">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="19:23:36.832+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="instruction.cxx:814">
    <![LOG[Successfully completed the action (start screen) with the exit win32 code 0]LOG]!><time="19:23:36.832+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="instruction.cxx:855">

    the log also shows the removeapps1.ps1 ran successfully, but apps are still there:

    <![LOG[Expand a string: powershell.exe -ExecutionPolicy Bypass -command "%scriptroot%\custom_Script\win10\RemoveAppsWin10\Removeapps1.ps1"]LOG]!><time="19:15:02.737+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:776">
    <![LOG[Expand a string: ]LOG]!><time="19:15:02.737+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:776">
    <![LOG[Start executing the command line: powershell.exe -ExecutionPolicy Bypass -command "%scriptroot%\custom_Script\win10\RemoveAppsWin10\Removeapps1.ps1"]LOG]!><time="19:15:02.737+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="instruction.cxx:731">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="19:15:02.737+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="instruction.cxx:760">
    <![LOG[Expand a string: WinPEandFullOS]LOG]!><time="19:15:02.737+240" date="10-01-2017" component="TSManager" context="" type="0" thread="5480" file="executionenv.cxx:776">
    <![LOG[Executing command line: powershell.exe -ExecutionPolicy Bypass -command "%scriptroot%\custom_Script\win10\RemoveAppsWin10\Removeapps1.ps1"]LOG]!><time="19:15:02.737+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="commandline.cpp:828">
    <![LOG[Process completed with exit code 0]LOG]!><time="19:20:37.878+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="commandline.cpp:1124">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="19:20:37.878+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="instruction.cxx:814">
    <![LOG[Successfully completed the action (Remove in-box apps) with the exit win32 code 0]LOG]!><time="19:20:37.878+240" date="10-01-2017" component="TSManager" context="" type="1" thread="5480" file="instruction.cxx:855">

    


    • Edited by Saeidans Tuesday, October 3, 2017 3:48 PM
    Tuesday, October 3, 2017 3:13 PM

All replies

  • Could I take a look at your BDD.log?

    As far as removing apps go: are you using the script from Michael Niehaus to perform app removal? If not, is there a logging function which might shed some light as to what is going on? Keep in mind that there are two cmdlets for app removal: Remove-AppxPackage and Remove-ProvisionedAppxPackage (the first removes apps for the current user and the second removes apps from the image).


    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Wednesday, October 4, 2017 9:00 AM
  • Hello Anton,

    I use the script from here, since Michael's script did not work.

    http://ccmexec.com/2015/08/removing-built-in-apps-from-windows-10-using-powershell/

    looks like the bdd is too big to fit here, is there a way to attach it?


    
    Wednesday, October 4, 2017 2:33 PM
  • You could always upload your bdd.log to OneDrive or any other file sharing service :)

    As to Michael's script: I never ever had any issues with it. Looking at Jörgen's script, it is based around the same idea. However, Michael's is more refined and can be used in different scenarios (for example in WinPE for offline servicing). 


    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Wednesday, October 4, 2017 5:37 PM