Can't install 0.58.0 #18047
Comments
mike-ward
added
Issue-Bug
|
cc: @jaimecbernardo @crutkas: Another issue with WinAppSDK101 |
|
@mike-ward @mshtang , Could you please install this first manually to check if it fixes the issue? https://aka.ms/windowsappsdk/1.0/1.0.3/windowsappruntimeinstall-1.0.3-x64.exe |
|
from admin console: |
|
I'm receiving the same error when attempting a manual install. When updating PowerToys through the PowerToys interface, the install fails quietly -- the install dialog box simply disappears with no error message. On this system I am logged in as a regular user, and I have a separate administrator level account for authorizing admin functions such as installs. I'm attempting the update from the regular user account with the admin authorization. @jaimecbernardo , I tried manually installing the As a regular user (note the In an elevated command prompt on the user account: |
|
@mike-ward and @jaimecbernardo: as a follow-up to my post, when I logged into the admin account and ran I've occasionally seen these sort of edge cases when using separate user and admin accounts. |
|
Thanks @pearson , Errors do seem different, though. Yours was access denied, so it makes sense that running as admin would fix it. |
|
@mike-ward , is your admin user different than the user trying to install it? |
|
Yes, admin/user accounts are different. |
|
That might be it. |
|
The results I posted were from an admin command prompt. Here are the results from the user account: |
|
Similar to microsoft/WindowsAppSDK#2469 and previous #18021, #18023, #18047 have reported this dependency failing to install and causing power toys update or install to fail. Windows App SDK 1.0.3 seems to be the culprit. This dependency is spitting several different errors. |
@jaimecbernardo , what's odd about this is that it makes a difference whether you're actually logged into an admin account, or whether you're logged in as a regular user but using an admin elevated command prompt. Given its |
I tried to manually install it and got the exact same errors as stated in here. I don't have a "super" admin account as the computer is managed by corp so I cannot do what is done here. If this helps: I do have a local admin and can usually install stuff on my machine without any problems. But it didn't work out in this case. |
@mshtang , |
No, this doesn't work out either. |
|
@mshtang, not sure what to do when you're getting "access denied" while installing a pre-requisite 🤷 . |
|
Hi, |
|
I've been able to solve the issue by changing "Developer settings" in Windows vide: Logged error message could be more informative on solution |
|
Some notes that might help: I'm getting the 0x80073d19 error, but looking in the Event Viewer under AppLocker (Application and Services Logs -> Windows -> AppLocker -> Package app-Deployment) I see an event id 8025 entry with error:
and the XML for the event: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-AppLocker" Guid="{cbda4dbf-8d5d-4f69-9578-be14aa540d22}" />
<EventID>8025</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x1000000000000000</Keywords>
<TimeCreated SystemTime="2022-05-09T18:49:23.4896843Z" />
<EventRecordID>577</EventRecordID>
<Correlation ActivityID="{59e17f71-5e22-0008-b0b9-f659225ed801}" />
<Execution ProcessID="39476" ThreadID="38828" />
<Channel>Microsoft-Windows-AppLocker/Packaged app-Deployment</Channel>
<Computer>abcd</Computer>
<Security UserID="S-1-5-qqqq" />
</System>
- <UserData>
- <RuleAndFileData xmlns="http://schemas.microsoft.com/schemas/event/Microsoft.Windows/1.0.0.0">
<PolicyNameLength>4</PolicyNameLength>
<PolicyName>APPX</PolicyName>
<RuleId>{00000000-0000-0000-0000-000000000000}</RuleId>
<RuleNameLength>1</RuleNameLength>
<RuleName>-</RuleName>
<RuleSddlLength>1</RuleSddlLength>
<RuleSddl>-</RuleSddl>
<TargetUser>S-1-5-qqqq</TargetUser>
<TargetProcessId>39476</TargetProcessId>
<PackageLength>49</PackageLength>
<Package>MicrosoftCorporationII.WindowsAppRuntime.Main.1.0</Package>
<FqbnLength>149</FqbnLength>
<Fqbn>CN=MICROSOFT CORPORATION, O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFTCORPORATIONII.WINDOWSAPPRUNTIME.MAIN.1.0\APPX\3.469.1654.00</Fqbn>
</RuleAndFileData>
</UserData>
</Event> |
|
@mwilsonray Is it possible to configure AppLocker with an exception for it? |
|
@jaimecbernardo I'm working on getting the exception approved, but it requires several reviews :-( |
|
This is a really long thread mixing multiple issues: #1 The original message said failure due to error 0x80073d19 == ERROR_DEPLOYMENT_BLOCKED_BY_USER_LOG_OFF. That error code had a text message of "An error occurred because a user was logged off" which is a bit misleading. A more recent definition is more helpful:
By default, Windows blocks deployment operations on special profiles. The term ‘special profile’ will cover roaming profiles, mandatory and super-mandatory profiles, temporary profiles and guest account profiles. Usually, it is recommended that you don’t allow deployment on such user profiles. You can find more information about AllowDeploymentInSpecialProfiles here. But remember, this isn't recommended. Installing packages in special profiles and then logging out and logging in with a different profile (special or not) can result in broken installations due to torn data -- some of that installation information was in that special profile when you installed and is now gone when you logged with a different profile. #2 #3 0x80073cff = ERROR_INSTALL_POLICY_FAILURE installing DDLM packages:
This occurs because the DDLM packages are Microsoft-signed (not Microsoft-Store-signed) which requires sideloading is allowed. This is enabled in desktop by default but the policy can be disabled by administrators (and it's disabled by default on server, in case you're installing there). This is a known issue under active discussion. See microsoft/WindowsAppSDK#2469 for more details. |
|
Thanks a lot for your insights here @DrusTheAxe 😄 |
|
@jukrb0x, any additional info on what the issue is for you as well? What error code? |
|
Got it to work by installing it with just a local admin account. If my account is using a microsoft online one it fails. |
|
This should've been fixed alongside #18021 since we're no longer installing Windows App SDK runtimes. |
jaimecbernardo
added
Resolution-Already Fixed/Doesn't Apply
|
|
|
[19F8:08FC][2022-11-30T13:34:08]i001: Burn v3.14.0.6526, Windows v10.0 (Build 22621: Service Pack 0), path: C:\WINDOWS\Temp{FD2F6CC2-37C9-4752-AEDD-77BFBE1F9135}.cr\PowerToysSetup-0.64.1-arm64.exe |
Microsoft PowerToys version
0.58.0
Running as admin
Area(s) with issue?
Installer
Steps to reproduce
Installer runs but does not complete. Displays error shown below.
✔️ Expected Behavior
installer succeeds.
❌ Actual Behavior
log file from install:
Other Software
No response
The text was updated successfully, but these errors were encountered: