none
April 2018 Rollup for Windows 10 breaks App-V Scripts?

    General discussion

  • From Sebastian Gernert's blog:

    "KB4093112

    Error : 

    0x0DF02925-000008AD

    We notice that with the Installation of the April 2018 Rollup for Windows 10 - you can no longer use App-V Scripting. We are investigating this. Until we have a solution, please do not install the April Rollup in order to continue using Scripting."

    https://blogs.msdn.microsoft.com/sgern/2018/04/12/april-2018-rollup-for-windows-10-und-server-2016-last-app-v-scripts-nicht-mehr-starten/

    We have confirmed this issue in Windows 10 1703. Any updates on a fix?

    Monday, April 16, 2018 2:49 PM

All replies

  • Not more than it will be fixed in one of the next Rollups.

    Roy Essers


    • Edited by Roy Essers Monday, April 16, 2018 6:58 PM
    Monday, April 16, 2018 6:45 PM
  • Confirmed issue on Windows 10 LTSB 2016 (1607). AddPackage scripts work, publishpackage scripts fail with "0x0DF02925-000008AD", after installing KB4093112.  Uninstalling the April 2018 patch resolves the issue.

    Submitted a case to Premiere support, no follow up yet.

    Monday, April 16, 2018 9:10 PM
  • Same here. Also breaks when starting a script from StartVirtualEnvironment
    Tuesday, April 17, 2018 7:12 AM
  • Same issue - Windows 10 1703 both x86 and x64. Started seeing issue after installing April 2018 patches.

    Microsoft - any chance you could at least get this on the "known issues" list for these builds?

    • Edited by Nick_B_935 Wednesday, April 18, 2018 12:24 PM
    Tuesday, April 17, 2018 6:34 PM
  • Also made a ticker and urged them to add this to the "know issues" list for the april patches.

    Roy Essers

    Thursday, April 19, 2018 9:36 AM
  • See the update on Sebastian's blog.  He indicates that there may be a private hotfix that you can get if you open a ticket.

    Tim


    App-V MVP & CTP Fellow. Author of AppV books: PowerShell with App-V 5, The Application Book, & Window Caching (http://www.tmurgent.com/Books)

    Thursday, April 19, 2018 9:32 PM
    Moderator
  • Same issues on 1703. Our observations:

    • KB4093107 (april rollup released on April 10th) contains version 10.0.15063.1029 of Appvscripting.dll
      This update breaks the app-v scripting functionality
    • KB4093117 (april rollup released on April 16th) contains a newer version (10.0.15063.1058) of Appvscripting.dll.
      This update does however not fix the app-v scripting functionality
    • Replacing the Appvscripting.dll file with an older version file (10.0.15063.936) on a patched system restores the app-v scripting functionality ! However, this is not supported as it involves taking ownership of the file away from trustedinstaller and setting new NTFS permissions so that it can be replaced.
    Thursday, April 26, 2018 6:21 AM
  • I successfully tested the private hotfix yesterday. It should be included in the next Rollup (May).Also check the updated blogpost.

    Roy Essers

    Thursday, April 26, 2018 8:01 AM
  • Can you send me the private hotfix?

    Jose Gonzalez

    Thursday, April 26, 2018 4:03 PM
  • To get private hotfixes, you need to log a call with Microsoft.

    Anyhow, the May Rollup is available and fixes this issue:
    1803 - KB4103721
    1709 - kb4103727
    1703 - KB4103731
    1607 - KB4103723


    Roy Essers



    • Edited by Roy Essers Wednesday, May 9, 2018 6:13 AM
    Wednesday, May 9, 2018 6:11 AM