-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows suddenly requires developer license for installation of classic installer #15546
Comments
This comment was marked as duplicate.
This comment was marked as duplicate.
Thanks for the report,
|
That is a different issue. Please follow https://files.community/docs/install#:~:text=Steps%20required%20for%20the%20%E2%80%9Cclassic%20installer%E2%80%9D%20version%20after%203/21/2024 |
Yes, Windows Store is disabled (via group policy aka company controlled likely), that's the issue at hand. After all, that's why I use the classic installer/choco package. |
If it's blocked by your company there isn't anything we can do, Why it work before I don't know but it possible Windows or your company updated to block it. |
Is developers really can't build app running without windows apps licensing system and can't make offline installer? Trends of next-generation apps... |
Licensing systems aren't new at all and if not disabled would work fine and there are offline installers |
Kinda translated (with the help of DeepL) like:
Translated with DeepL:
|
There isn't anything we can do. It would be an issue with your system or a company policy blocking the use of Windows update/Microsoft store features. |
Thing is, the installation has worked before I tried (to upgrade to) the v3.2.4 of this IIRC, as said. |
Did you try installing via PowerShell? |
Yes, even using the workaround suggested here: > & { $ProgressPreference = 'Ignore'; Import-Module Appx 3>$null }
> Add-AppxPackage -Path "*****\Microsoft.WindowsAppRuntime.1.5.msix"
> Add-AppxPackage -Path "*****\Files.Package_3.4.1.0_x64_arm64_Stable.msixbundle"
Add-AppxPackage : Fehler bei Bereitstellung. HRESULT: 0x80073CFF, Für die Installation dieser Anwendung wird eine
Windows-Entwicklerlizenz oder ein sideloadfähiges System benötigt.
Fehler beim Bereitstellen des Pakets Files_3.4.1.0_neutral_split.scale-125_1y0xx7n9077q4 mit Paketursprung Unknown, da
keine gültige Lizenz- oder Querladerichtlinie angewendet werden konnte. Möglicherweise ist eine Entwicklerlizenz
(http://go.microsoft.com/fwlink/?LinkId=233074) oder eine Enterprise-Querladekonfiguration
(http://go.microsoft.com/fwlink/?LinkId=231020) erforderlich.
HINWEIS: Wenn Sie weitere Informationen wünschen, suchen Sie im Ereignisprotokoll nach [ActivityId]
a1f9852b-ceb0-0002-439b-7ba2b0ceda01, oder verwenden Sie die Befehlszeile Get-AppxLog -ActivityID
a1f9852b-ceb0-0002-439b-7ba2b0ceda01
In Zeile:1 Zeichen:1
+ Add-AppxPackage -Path "*****\Files.Package_3.4 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (*****...able.msixbundle:String) [Add-AppxPackage], Exception
+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand Same error. As you can see installing The gist seems to be:
So I guess the package is somehow not signed or signed in a different (not so much trusted?) way or something like that... |
Description
For me Windows Store is blocked (likely by group policy), so I cannot install the app from Windows Store. The traditional installation has worked in the past, but now fails, somehow?
Steps To Reproduce
Download classic installer from https://files.community/download and try to install it.
The same happens when I
choco upgrade
it:Roughly translated (with DeepL):
Requirements
Files Version
3.4.1.0
Windows Version
10.0.19045.4291
Log File
N/A
Edition Windows 10 Enterprise
Version 22H2
Installiert am ******
Betriebssystembuild 19045.4291
Leistung Windows Feature Experience Pack 1000.19056.1000.0
/cc @w0 as apparently being the maintainer of the choco package, although I want to stress the issue is reproducible with the official installer.
The text was updated successfully, but these errors were encountered: