files-community / Files

Building the best file manager for Windows
https://files.community
MIT License
32.89k stars 2.1k forks source link

Bug: 3.5.1 won't install because PRI file fails to merge #15699

Closed ByronGarbutt closed 4 days ago

ByronGarbutt commented 5 days ago

Description

App installation failed with error message: Merge failure for shared merged PRI file : error 0x80070490 : Cannot register the FilesPreview_3.5.1.0_x64__1y0xx7n9077q4 package because there was a merge failure with the following file: C:\Program Files\WindowsApps\FilesPreview_3.5.1.0_neutral_split.scale-125_1y0xx7n9077q4\resources.pri (0x80070490)

Steps To Reproduce

Apply 3.5.1 update

Requirements

Files upgraded from 3.5 to 3.5.1

Files Version

3.5.1

Windows Version

11.0.26120.961

Log File

debug.log

0x5bfa commented 4 days ago

0x80070490 seems to be an error code from Microsoft Store components.

Can you try to reinstall the app (firstly export your settings from Settings > Advanced) If not fixed, try "DISM.exe /Online /Cleanup-image /Scanhealth"

deviaze commented 4 days ago

Exact same issue here (on reinstall). Last night I tried updating Files Preview but it failed silently & refused to open after that. Uninstalled and reinstalled Files Preview and got the same error message as ByronGarbutt above.

specs: Surface Pro 9 (intel) Edition Windows 11 Home Version 23H2 OS build 22631.3737 Experience Windows Feature Experience Pack 1000.22700.1009.0

ByronGarbutt commented 4 days ago

0x80070490 seems to be an error code from Microsoft Store components.

Can you try to reinstall the app (firstly export your settings from Settings > Advanced) If not fixed, try "DISM.exe /Online /Cleanup-image /Scanhealth"

Ran sfc /scannow and dism commands ScanHealth & RestoreHealth, rebooted, same issue ... tried it on another laptop with 23H2, same issue

yaira2 commented 4 days ago

@Josh65-2201 can you repro this?

Josh65-2201 commented 4 days ago

Yes, Tried built in updater, PowerShell and uninstalling then trying to install

yaira2 commented 4 days ago

This is resolved with v3.5.2.