CheckUpdateAvailabilityAsync returns error on win 1809 (but it works fine on 1909)

%3CLINGO-SUB%20id%3D%22lingo-sub-2246255%22%20slang%3D%22en-US%22%3ECheckUpdateAvailabilityAsync%20returns%20error%20on%20win%201809%20(but%20it%20works%20fine%20on%201909)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2246255%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EWhen%20checking%20the%20update%20for%20the%20WPF%20app%20packaged%20into%20MSIX%20together%20with%20Package%20Support%20Framework%2C%20CheckUpdateAvailabilityAsync%20method%20returns%20such%20a%20result%20with%20Extended%20error%3A%20%22The%20.appinstaller%20file%20is%20invalid.%20(Exception%20from%20HRESULT%3A%200x8008020C)%22%20for%20machines%20with%20Win%2010%201809.%20For%20other%20machines%20which%20are%20running%201909%2C%20the%20update%20is%20successfully%20found.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EI'm%20using%20code%20from%20docs%20example%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fnon-store-developer-updates%23updating-packages-deployed-using-an-app-installer-file%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EUpdate%20non-Store%20published%20apps%20from%20your%20code%20-%20MSIX%20%7C%20Microsoft%20Docs%3C%2FA%3E%3A%3C%2FSPAN%3E%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-csharp%22%3E%3CCODE%3E_currentPackage%20%3D%20_pm.FindPackageForUser(string.Empty%2C%20Package.Current.Id.FullName)%3B%0A%20var%20result%20%3D%20await%20_currentPackage.CheckUpdateAvailabilityAsync()%3B%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%3CSPAN%3EPackage.Current.Id.FullName%20is%20successfully%20recognized%20on%20both%201809%20and%201909.%20The%20only%20difference%20is%20for%20CheckUpdateAvailabilityAsync%20call.%20What%20does%20this%20error%20code%20mean%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAttaching%20my%20appinstaller%20file%20(it's%20default%20one%20generated%20from%20VS%20%22publish%22).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

When checking the update for a WPF app packaged into MSIX together with Package Support Framework, CheckUpdateAvailabilityAsync method returns such a result with Extended error: "The .appinstaller file is invalid. (Exception from HRESULT: 0x8008020C)" for machines with Win 10 1809. For other machines which are running 1909, the update is successfully found.

I'm using code from docs example Update non-Store published apps from your code - MSIX | Microsoft Docs:

 

_currentPackage = _pm.FindPackageForUser(string.Empty, Package.Current.Id.FullName);
 var result = await _currentPackage.CheckUpdateAvailabilityAsync();

 

Package.Current.Id.FullName is successfully recognized on both 1809 and 1909. The only difference is for CheckUpdateAvailabilityAsync call. What does this error code mean?

Attaching my appinstaller file (it's default one generated from VS "publish").

 

6 Replies
Hi! Thank you for posting your question. On the 1809 device, can you please file a Feedback Hub bug under "Windows Installation And Setup" -> "App Installation and Launch issues" with the “take screenshot for each step” option enabled? We will take a look.

@Dian Hartono 

Hi, thanks for the reply. Could you be more specific? I don't understand what should I do.

Sure! On your Windows 10 machine that is on a 1809 Build, please go to the Feedback Hub App by searching for it on the Start menu or you can use Windows Key + F to open it. Please describe your repro steps. When you choose a Category that best describes your issue, select "Windows Installation And Setup" -> "App Installation and Launch issues" . If you do not see that option, you can also choose the category that best describes the situation. Please than choose to record the issue by reproducing the update issue and select “take screenshot for each step”. If you can also than share the your feedback title, we can also query it ourselves.
Hello. The solution is in your post!
Version 1809 is outdated, so not compatible and just update the machine - to version 1909 and after the problem! Searching for reasons in this case is pointless, and reporting to the feedback center will end in archiving and the topic closed!
A Microsoft employee can't only promote reporting to the feedback center in my opinion, i would point it to Microsoft Support!
MTC - is a Forum, but not technical support.
Good luck Andrew. Please write what do you think about my comment?

@AndrzejX 

Thanks for great tip :D

According to docs it should work on 1809. I can't control my organization upgrade plan. Users will get newer version eventually but some of them are not there yet.

Hello. Your additional information explains and justifies - further analysis ! Forgive me for not being able to understand why you don't need an update, sometimes the entries are imprecise and don't give a complete picture of the circumstances that force you to look for solutions! IT is a constant struggle with obstacles - starting with human errors and other independent obstacles. MTC members are reading this you will probably get help! Thank you very much