Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Verified Answer
  • Replies replies
    7
  • Subscribers subscribers
    4
  • Views views
    2038
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Packaged applications will not launch after Win 10 1803->1909 update, can't launch studio

Bettencourtm

We have found that our library of packaged applications do not work after updating our Windows PC's past 1803.  The applications were mostly packaged on a PC using 1803, when we moved to Windows 10 last year using MFDC-12.3.

When launching a packaged application we get an error that reads:

"The application has encountered an error: The specified path is invalid (0x800700A1)"

When launching the 12.5 or 12.4 Studio:

"Please set registry key HKLM\Software\Microsoft\.NETFramework\InstallRoot to point to the .net framework install location" (I checked, and it does. Reinstalled .net frameworks as well, no avail.)

Is there anything we can do to let our applications launch?  We had to repackage all our applications when we moved to windows 10. Will we have to repackage for every 6-month update of windows? This would be a major headache.

 

 

 

 

Parents
  • 0  

    In regards to the Studio 12.4 and 12.5 issue, check in your Customer Portal to see if you have MFDC 12.6 available.  If not, try opening an SR to see if support can get you a copy, it's in the process of being released.

    I was able to get a copy via my software portal earlier in the week, but the customer I was  working with did not have it yet.  If I had to guess, it would likely resolve the Windows 1909 issue, though I have yet to test 1909 with MFDC.

    In regards to building the Apps, this is sometimes necessary when Windows changes underlying security.  It tends to be uncommon, but you can actually open the Virtual EXE directly in Admin Studio and then just tell it to rebuild.   Quite a quick process.  

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

Reply
  • 0  

    In regards to the Studio 12.4 and 12.5 issue, check in your Customer Portal to see if you have MFDC 12.6 available.  If not, try opening an SR to see if support can get you a copy, it's in the process of being released.

    I was able to get a copy via my software portal earlier in the week, but the customer I was  working with did not have it yet.  If I had to guess, it would likely resolve the Windows 1909 issue, though I have yet to test 1909 with MFDC.

    In regards to building the Apps, this is sometimes necessary when Windows changes underlying security.  It tends to be uncommon, but you can actually open the Virtual EXE directly in Admin Studio and then just tell it to rebuild.   Quite a quick process.  

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

Children
  • 0   in reply to   

    I don't have any issue launching either Studio 12.5 or 12.6 on a freshly Built Windows 10 1909 System.

    Not sure if an OS Upgrade could have broken studio, though I've never seen that in the past.

    In regards to Win10 OS Upgraded requiring Virtual Apps to be rebuilt,  the first time this was widely seen was with 1803 needing MFDC at least 12.3.  Prior to that, even virtual apps many years old predating when the product was called ZAV vs MFDC were still working.  1903 did seem to cause some issues needing MFDC 12.5, but there were less reported issues around that....not sure why.

    I would expect Win1909 to have any extra issues, since it should be the same as 1903 under the hood with a few added feature w/o any changes to the core OS itself with all 1903 and 1909 patches being the exact same files..... 

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.