User Profile
martijnk79
Brass Contributor
Joined Feb 22, 2019
User Widgets
Recent Discussions
Re: Auto-LogOff User after closing last application
Old topic I know but we solved this by setting the GPO: - Set time limit for active but idle Remote Desktop Services sessions to 1 hour. - Set time limit for logoff of RemoteApp sessions to Immediately. I've tested this and even when OneDrive launches with the app, as soon as I close the last app my session logs off. You can also set the last setting to one minute. Because when the user closes the last app and immediately wants to start a new app you may run into issues when the logoff is still in process. We are still testing this.Re: MSIX Breakaway in 22h2+ (win 10 + 11)
mattplan8 Thanks for the extended writeup! Unfortunately, it still doesn't work for me. My application is Microsoft Navision and it calls Excel or Word from a couple of buttons in the toolbar. I have no control to what those buttons do, or how they call the Office apps. But with your method, launching Navision with the -PreventBreakway doesn't change anything. The entire application just crashes when I launch Word/Excel from the MSIX app (Excel/Word never launch) and I get an error in the application log. With App-V or local install, it all just works fine (btw I'm using Win11 multisession but I get the same behavior with Windows Server 2019). You would assume that any child process within your MSIX container will be launched within the container, just like App-V used to handle it. I see no reason why to launch it outside of it. Then again, I might have a totally different problem with this app. But all Navision apps, all versions behave exactly the same when ran from MSIX. I also tried to pre-launch Excel from the container using your same command, so Excel is already open from within the container and it should be using that window. But still, same result. The app just crashes with no specific error message. I will do some other testing as well with other apps that open child processes, see if they work with your workaround. Because it might just be Navision acting up. So thanks again for this post, very helpful! Faulting application name: finsql.exe, version: 5.0.26084.0, time stamp: 0x47b39d56 Faulting module name: finsql.exe, version: 5.0.26084.0, time stamp: 0x47b39d56 Exception code: 0xc0000005 Fault offset: 0x001e85cf Faulting process id: 0x2ca8 Faulting application start time: 0x01da2d00e342d297 Faulting application path: C:\Program Files (x86)\Microsoft Dynamics NAV\CSIDE Client\finsql.exe Faulting module path: C:\Program Files (x86)\Microsoft Dynamics NAV\CSIDE Client\finsql.exe Report Id: dd24e03c-992a-44a8-b4b8-836deb47bf46 Faulting package full name: FRF-P_4.0.0.0_x64__rt6ps99bwbnfa Faulting package-relative application ID: FRFRe: MSIX Breakaway in 22h2+ (win 10 + 11)
mattplan8 I have the same issue with apps calling Word or Excel outside the container while they should start inside. So I reverted those back to App-V. Can you tell me how your workaround works? How would I prevent breakaway of these apps? Do you mean you just launch the main app with the command invoke-commandindesktoppackage -preventbreakaway? And then all child processes will launch within the container?Re: MSI-X app crashes when calling Office app
Hi Timothy, yes the package is using PSF because the executable has to run with specific parameters. Unfortunately I don't have source code access to the app, I guess I'll have to wait for Office 365 MSIX support. And maybe use shared container by that time? The problem is that 90% of our apps call Office for some functionality.Re: File redirection question
Yes I did some research on it and it seems to be by design that it writes to that directory. No big deal since FSLogix is saving that location to the profile. So I just removed the redirecttargetbase, not redirecting anything right now and will leave it like this. It's just that some users want to manipulate that file, so I just have to instruct them of the new location. Thanks.MSIX icon troubles
Hello, I'm converting several App-V packages to MSI-X. For most packages this works fine, others work too but the icon is not working. You get an application without an icon, so like an empty command window (just regular executable icon). I wonder where or how to fix this as I have no clue.MSI-X app crashes when calling Office app
Hello, I've repackaged my app to MSI-X app attach and loaded it into an Azure Virtual Desktop. The app works fine however, when calling Word/Excel it just crashes with no error. I've attached the error report below, don't know if it's useful. But do I need to do anything special to call Word/Excel/Outlook from an app? I have another MSI-X app and it seems to work fine there. Thanks! Version=1 EventType=MoAppCrash EventTime=133458955554305718 ReportType=2 Consent=1 UploadTime=133458955558680726 ReportStatus=268435456 ReportIdentifier=37205d62-0e98-4f30-8c2b-9943319bd614 IntegratorReportIdentifier=3de21733-b201-4849-9325-35a26708a235 Wow64Host=34404 Wow64Guest=332 NsAppName=praid:FRF OriginalFilename=FINSQL.EXE AppSessionGuid=000038f8-0004-0014-9714-51773624da01 TargetAppId=U:FRF-P_4.0.0.0_x64__rt6ps99bwbnfa!FRF TargetAppVer=4.0.0.0_x64_!2008//02//14:01:45:58!a5e7e7!finsql.exe BootId=4294967295 TargetAsId=7141 IsFatal=1 EtwNonCollectReason=1 Response.BucketId=7ee19f45fa7d8a681cdc4848e6161339 Response.BucketTable=5 Response.LegacyBucketId=2079616605873378105 Response.type=4 Sig[0].Name=Package Full Name Sig[0].Value=FRF-P_4.0.0.0_x64__rt6ps99bwbnfa Sig[1].Name=Application Name Sig[1].Value=praid:FRF Sig[2].Name=Application Version Sig[2].Value=5.0.26084.0 Sig[3].Name=Application Timestamp Sig[3].Value=47b39d56 Sig[4].Name=Fault Module Name Sig[4].Value=finsql.exe Sig[5].Name=Fault Module Version Sig[5].Value=5.0.26084.0 Sig[6].Name=Fault Module Timestamp Sig[6].Value=47b39d56 Sig[7].Name=Exception Code Sig[7].Value=c0000005 Sig[8].Name=Exception Offset Sig[8].Value=001e85cf DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.22631.2.0.0.16.175 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=0000 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=00000000000000000000000000000000 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=0000 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=00000000000000000000000000000000 UI[2]=C:\Program Files\WindowsApps\FRF-P_4.0.0.0_x64__rt6ps99bwbnfa\VFS\ProgramFilesX86\Microsoft Dynamics NAV\CSIDE Client\finsql.exe LoadedModule[0]=C:\Program Files\WindowsApps\FRF-P_4.0.0.0_x64__rt6ps99bwbnfa\VFS\ProgramFilesX86\Microsoft Dynamics NAV\CSIDE Client\finsql.exe LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll LoadedModule[2]=C:\Windows\System32\KERNEL32.DLL LoadedModule[3]=C:\Windows\System32\KERNELBASE.dll LoadedModule[4]=C:\Windows\SYSTEM32\tsappcmp.dll LoadedModule[5]=C:\Windows\System32\msvcrt.dll LoadedModule[6]=C:\Windows\System32\RPCRT4.dll LoadedModule[7]=C:\Windows\System32\combase.dll LoadedModule[8]=C:\Windows\System32\ucrtbase.dll LoadedModule[9]=C:\Windows\System32\USER32.dll LoadedModule[10]=C:\Windows\System32\win32u.dll LoadedModule[11]=C:\Windows\System32\GDI32.dll LoadedModule[12]=C:\Windows\System32\gdi32full.dll LoadedModule[13]=C:\Windows\System32\msvcp_win.dll LoadedModule[14]=C:\Windows\System32\ADVAPI32.dll LoadedModule[15]=C:\Windows\System32\sechost.dll LoadedModule[16]=C:\Windows\System32\IMM32.DLL LoadedModule[17]=C:\Program Files\WindowsApps\FRF-P_4.0.0.0_x64__rt6ps99bwbnfa\PsfRuntime32.dll LoadedModule[18]=C:\Windows\System32\SHELL32.dll LoadedModule[19]=C:\Windows\System32\ole32.dll LoadedModule[20]=C:\Windows\System32\WS2_32.dll LoadedModule[21]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.22621.2506_none_6eb991c088050a06\COMCTL32.dll LoadedModule[22]=C:\Windows\SYSTEM32\WININET.dll LoadedModule[23]=C:\Windows\SYSTEM32\SHFOLDER.dll LoadedModule[24]=C:\Windows\System32\comdlg32.dll LoadedModule[25]=C:\Windows\System32\shcore.dll LoadedModule[26]=C:\Windows\SYSTEM32\hlink.dll LoadedModule[27]=C:\Windows\SYSTEM32\msi.dll LoadedModule[28]=C:\Windows\System32\SHLWAPI.dll LoadedModule[29]=C:\Windows\System32\OLEAUT32.dll LoadedModule[30]=C:\Windows\SYSTEM32\MSIMG32.dll LoadedModule[31]=C:\Windows\SYSTEM32\WINSPOOL.DRV LoadedModule[32]=C:\Windows\SYSTEM32\iertutil.dll LoadedModule[33]=C:\Windows\SYSTEM32\bcrypt.dll LoadedModule[34]=C:\Windows\SYSTEM32\kernel.appcore.dll LoadedModule[35]=C:\Windows\SYSTEM32\windows.staterepositorycore.dll LoadedModule[36]=C:\Windows\System32\bcryptPrimitives.dll LoadedModule[37]=C:\Windows\system32\uxtheme.dll LoadedModule[38]=C:\Windows\SYSTEM32\ACTIVEDS.DLL LoadedModule[39]=C:\Windows\SYSTEM32\adsldpc.dll LoadedModule[40]=C:\Windows\System32\WLDAP32.dll LoadedModule[41]=C:\Windows\SYSTEM32\SECUR32.DLL LoadedModule[42]=C:\Windows\System32\MSCTF.dll LoadedModule[43]=C:\Windows\SYSTEM32\Ctl3d32.DLL LoadedModule[44]=C:\Windows\SYSTEM32\textinputframework.dll LoadedModule[45]=C:\Windows\SYSTEM32\CoreMessaging.dll LoadedModule[46]=C:\Windows\SYSTEM32\CoreUIComponents.dll LoadedModule[47]=C:\Windows\SYSTEM32\wintypes.dll LoadedModule[48]=C:\Windows\SYSTEM32\CRYPTBASE.DLL LoadedModule[49]=C:\Windows\SYSTEM32\CRYPTSP.dll LoadedModule[50]=C:\Windows\system32\rsaenh.dll LoadedModule[51]=C:\Windows\System32\clbcatq.dll LoadedModule[52]=C:\Windows\SYSTEM32\windows.storage.dll LoadedModule[53]=C:\Windows\SYSTEM32\TextShaping.dll LoadedModule[54]=C:\Program Files\WindowsApps\FRF-P_4.0.0.0_x64__rt6ps99bwbnfa\VFS\ProgramFilesX86\Microsoft Dynamics NAV\CSIDE Client\NDBCS.DLL LoadedModule[55]=C:\Windows\SYSTEM32\VERSION.dll LoadedModule[56]=C:\Windows\SYSTEM32\ODBC32.dll LoadedModule[57]=C:\Windows\System32\CRYPT32.dll LoadedModule[58]=C:\Windows\SYSTEM32\DPAPI.DLL LoadedModule[59]=C:\Windows\system32\SQLSRV32.dll LoadedModule[60]=C:\Windows\system32\NETAPI32.dll LoadedModule[61]=C:\Windows\SYSTEM32\SspiCli.dll LoadedModule[62]=C:\Windows\SYSTEM32\odbccp32.dll LoadedModule[63]=C:\Windows\SYSTEM32\DBNETLIB.DLL LoadedModule[64]=C:\Windows\SYSTEM32\security.dll LoadedModule[65]=C:\Windows\System32\msv1_0.DLL LoadedModule[66]=C:\Windows\SYSTEM32\NtlmShared.dll LoadedModule[67]=C:\Windows\SYSTEM32\ntdsapi.dll LoadedModule[68]=C:\Windows\SYSTEM32\DSPARSE.DLL LoadedModule[69]=C:\Windows\system32\mswsock.dll LoadedModule[70]=C:\Windows\SYSTEM32\DNSAPI.dll LoadedModule[71]=C:\Windows\SYSTEM32\IPHLPAPI.DLL LoadedModule[72]=C:\Windows\System32\NSI.dll LoadedModule[73]=C:\Windows\System32\rasadhlp.dll LoadedModule[74]=C:\Windows\System32\fwpuclnt.dll LoadedModule[75]=C:\Windows\System32\schannel.dll LoadedModule[76]=C:\Windows\SYSTEM32\ncrypt.dll LoadedModule[77]=C:\Windows\SYSTEM32\NTASN1.dll LoadedModule[78]=C:\Windows\system32\ncryptsslp.dll LoadedModule[79]=C:\Windows\SYSTEM32\netbios.dll LoadedModule[80]=C:\Windows\System32\msxml3.dll LoadedModule[81]=C:\Windows\System32\urlmon.dll LoadedModule[82]=C:\Windows\System32\srvcli.dll LoadedModule[83]=C:\Windows\System32\netutils.dll LoadedModule[84]=C:\Windows\System32\coml2.dll LoadedModule[85]=C:\Windows\SYSTEM32\dwmapi.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=22631 OsInfo[3].Key=ubr OsInfo[3].Value=2715 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=1033 OsInfo[7].Key=geoid OsInfo[7].Value=244 OsInfo[8].Key=sku OsInfo[8].Value=175 OsInfo[9].Key=domain OsInfo[9].Value=1 OsInfo[10].Key=prodsuite OsInfo[10].Value=16 OsInfo[11].Key=ntprodtype OsInfo[11].Value=3 OsInfo[12].Key=platid OsInfo[12].Value=10 OsInfo[13].Key=sr OsInfo[13].Value=0 OsInfo[14].Key=tmsi OsInfo[14].Value=11306 OsInfo[15].Key=osinsty OsInfo[15].Value=2 OsInfo[16].Key=iever OsInfo[16].Value=11.1.22621.0-11.0.1000 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=16384 OsInfo[19].Key=svolsz OsInfo[19].Value=126 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=220506 OsInfo[22].Key=bldtm OsInfo[22].Value=1250 OsInfo[23].Key=bldbrch OsInfo[23].Value=ni_release OsInfo[24].Key=bldchk OsInfo[24].Value=0 OsInfo[25].Key=wpvermaj OsInfo[25].Value=0 OsInfo[26].Key=wpvermin OsInfo[26].Value=0 OsInfo[27].Key=wpbuildmaj OsInfo[27].Value=0 OsInfo[28].Key=wpbuildmin OsInfo[28].Value=0 OsInfo[29].Key=osver OsInfo[29].Value=10.0.22621.2715.amd64fre.ni_release.220506-1250 OsInfo[30].Key=buildflightid OsInfo[31].Key=edition OsInfo[31].Value=ServerRdsh OsInfo[32].Key=ring OsInfo[32].Value=Retail OsInfo[33].Key=expid OsInfo[33].Value=MD:283BAEF,ME:25762F0,ME:27B9BC4,ME:28279A6 OsInfo[34].Key=fconid OsInfo[34].Value=19195476,0,2,0;35681102,0,1,0;36803287,0,2,1;36803295,0,2,0;38277973,0,1,1;39145991,0,2,0;39263329,1,2,0;39281392,0,2,0;40025975,0,1,0;40616880,0,1,0;40883769,0,1,0;40981503,0,1,0;41135193,0,1,1;41137130,0,1,0;41342175,0,1,0;41655236,0,2,0;42105254,0,2,0;43772553,0,1,0;43844371,0,1,0;43978769,0,1,1;44325080,0,1,0;44521793,0,1,0;44552141,0,1,0;44776738,0,2,0;45185354,0,2,0;45796396,0,2,0;46551074,0,1,0;46557400,0,1,0 OsInfo[35].Key=containerid OsInfo[36].Key=containertype OsInfo[37].Key=edu OsInfo[37].Value=0 OsInfo[38].Key=servicinginprogress OsInfo[38].Value=0 OsInfo[39].Key=featureupdatependingreboot OsInfo[39].Value=0 FriendlyEventName=Stopped working ConsentKey=MoAppCrash AppName=Microsoft Dynamics NAV Client executable for SQL server AppPath=C:\Program Files\WindowsApps\FRF-P_4.0.0.0_x64__rt6ps99bwbnfa\VFS\ProgramFilesX86\Microsoft Dynamics NAV\CSIDE Client\finsql.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=DBB205B725471C348D5F01C422813589 MetadataHash=-784633231Re: Application only working for admin because of missing folders
Hi bit of a late reply but this only happens when the user has an FSLogix profile. If there is a normal roaming profile the application works. With an fslogix profile the app gives 0xC0000279 error in process monitor when trying to create the folder.Re: File redirection question
Thanks for the extensive answer! Option 1 would be sufficient for us, but somehow it's not working. By adding the 'isExclusion' entry I assume you mean in the packager I go to files ,right-click the directory and choose 'Add Exclusion' is what I did. Am I correct? I also tried to add '[{AppData}]' to the global exclusion list but files still appear under AppData\Local\Packages\<PackageName>\LocalCache\Roaming. Which is weird, because the TEMP directory is excluded as well and those do show up outside of the package.File redirection question
Hi, This file redirection feature is very confusing to me. I have an application that writes to the temp folder (in localappdata) and the roaming appdata folder. Right now these files are stored in localappdata\packages\appname\localcache (or something like that). I want to store these files in their original location outside the package. So in appdata\roaming and in appdata\local\temp on the normal drive, so native. Can this be achieved with file redirection? Let's say I want to redirect all localappdata files and all roaming appdata files. Would this be the config or do I need something else? The base and patterns is not really clear to me. I appreciate any help. Thanks. "redirectedPaths": { "knownFolders": [ { "id": "LocalAppData", "relativePaths": [ { "base": "C:", "patterns": [ ".\\" ] } ] }, { "id": "RoamingAppdata", "relativePaths": [ { "base": "C:", "patterns": [ ".\\"Re: MSIX access control server 2019 / Citrix
Well I can answer my own question I found a way to do this with Applocker. Downside is that the shortcut remains visible for users that don't have access so if someone knows a better way let me know. Could be per user publishing but on multi-session VDI that's not really a great solution so I think this is the way to go.
