sqlitebrowser / sqlitebrowser/sqlitebrowser

Issues installing over previously installed older versions

Open
#1,771 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

packaging windows windows-installer
Dominant language
C++
Stars
24.6k
Forks
2.4k
Avg merge
3d 49m
Merged PRs (30d)
3

Description

Details for the issue

What did you do?

After updating from Windows 10 Pro 1803 to 1809 yesterday, my system notified me my old 3.0.8 sqlitebrowser was disabled (and in fact it was removed during the upgrade). So, I grabbed the latest version 3.11.1 (x64) and tried installing it.

What did you expect to see?

I expected it to at least install.

What did you see instead?

When the options had been selected and the install began, it failed saying it couldn't be installed. If I had more info (like a log) I would share it, but it doesn't appear the install creates one.

How'd you manage to work around this vexing issue?

I've never seen Windows do this before, so I was perplexed by it. I don't care if night mode works, so long as I can run the app. Interestingly, it suggested a reboot would be required when I attempted the install (but it never got that far).

I tried the slightly older portable version and it seemed to work. Then I used LessMSI to manually extract the contents of DB.Browser.for.SQLite-3.11.1-win64.msi. Within it, I found two folders: DB Browser for SQLite and System64. I'm not sure what the contents of System64 are necessary for (is this what the installer warned I'd need to reboot for?) but simply running DB Browser for SQLite\DB Browser for SQLite.exe worked fine (I just created a quick DB to try it out). I moved that folder where I want to run this from and so far, so good.

So, the purpose of this ticket is to let you know I may not be the only person running into this, and that the very latest regular channel Windows 10 seems unwilling to install this normally. There's a slightly hacky solution to it (manually extracting the msi, etc.), and the System64 files strike me as odd - I'm pretty sure these (or later versions thereof) are fully redundant and shouldn't be getting installed at all on Windows 10:

https://docs.microsoft.com/en-us/uwp/win32-and-com/win32-apis

Useful extra information

The info below often helps, please fill it out if you're able to. :)

What operating system are you using?
  • Windows: ( _version: 10 Pro 1809 fully up-to-date, using night mode )
  • Linux: ( distro: ___ )
  • Mac OS: ( version: ___ )
  • Other: ___
What is your DB4S version?
  • 3.11.1
  • 3.11.0
  • 3.10.1
  • Other: ___
Did you also

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing installation of DB.Browser.for.SQLite-3.11.1-win64.msi on Windows 10 Pro 1809, comparing it with the portable version and the extracted DB Browser for SQLite executable. Inspect the System64 contents and installer behavior; done means identifying why the MSI fails and confirming a normal installation path.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.