FIXED: Re: Frescobaldi: Weird error with 3.3.0 (OT?)

[Stephan Schöll]

I tried to help with some C++ Redistributables according to advice in
some posts. But all failed saying that a newer version is already installed.

I tried to uninstall 3.3.0 and install 3.2 for comparison purposes. And
yet, some similar error occured. I uninstalled any Frescobaldi
installation and noticed that nevertheless there is a C:\Program Files
(x86)\Frescobaldi folder full of plenty of stuff, among many with Qt5 or
similar in their name.

So I removed this folder (asks for admin permissions) and reinstalled
3.3.0 - successfully ;-)

So to me it seems that the uninstaller doesn't do a clean job.

- Stephan

On 30.04.2023 20:11, Stephan Schöll wrote:
> Jean,
>
> It's an older Thinkpad, and I thought, that I always installed OS
> updates timely when published / recommended.
>
> But checking for this puzzled me: build 19044 seems to be 21H2, but when
> checking for updates I get
>
> I update installed SW quite frequently and never had issues with any of
> them.
>
>
> Am 29.04.2023 um 21:56 schrieb Jean Abou Samra:
> > > Le 29 avr. 2023 à 21:37, Stephan Schöll <music@gmx.ch> a écrit :
> > >
> > > 
> > >
> > > On one of my Windows 10 computers I updated Frescobaldi by
> > >
> > > 1. unistalling 3.0.1.
> > >
> > > 2. installing 3.3.0 with the installer from the Frescobaldi website
> > >
> > > At the end of the installation process I guess the installer wants to
> > > start Frescobaldi. But instead I get this message with references to
> > > folders that definitely don't exist on my machine (C:\Python,
> > > D:\Users\Jones...)
> >
> >
> > Don’t worry about these. They are paths on the machine of the person
> > who built the installer.
> >
> >
> > > I uninstall and reinstalled again but without success.
> > >
> > > Is there anybody who could give me some advice, either what to do or
> > > where to post in case this is OT?
> >
> > Unfortunately, the error message is not very helpful. (I dare hope
> > that on Linux you would at least have gotten the name of the missing
> > symbol.)
> >
> > Anyway. Maybe your OS is too old? What precise version of Windows 10
> > is this? Did you upgrade it recently?