I have a Pi4B 4GB running Astroberry 2.0.3 just fine.

I wanted to get a second Pi4B 4GB running Astroberry 2.0.3, but for some reason, it's having major problems. I know the second Pi4B works as it runs with raspiosbuster just fine. But with Astroberry, it sometimes stops booting, sometimes stops in the middle of the Astroberry desktop graphic, and sometimes boots all the way but then locks up for several minutes when I move the attached mouse. 

This Pi is connected to a television, keyboard, and mouse. I have tried several different microSD cards, plus I redownloaded 2.0.3 and tried from that. Same result.

I just tried the "new" Astroberry 2.0.3 microSD card in my first Pi4B and it works. 

Thoughts?

just clone the SD CARD from the good machine to other one
I use Lexar 633x cards or samsung evo u3

I have tried this image in the "working" pi and it works fine. 

I am intrigued with your idea, though. It couldn't hurt. Question - how do I do the clone?

In windows you can use a software like Win32DiskImager that create an image file of your SD card and then you can write it on another SD.
Take care that NEW SD must be the same o greather than the original sd, due to the space of the image.
On raspbianos there is present a tool named SD card copier (or similar) that can copy running SD card on another connected via USB.
In this case I do not think the sd size must mach

Thank you! Very interesting.

I have had *some* success. I inserted the SD card into a PiZero I have, and it came up fine. I then attempted to do an update/upgrade to see if maybe that would help. Unfortunately, the PiZ doesn't have a lot of horse power and updates got to 96% before CPU went to 100%. However, I was able to do a safe shutdown.

I transferred the card to my "broken" Pi, and this time it came up all the way. It looked like it was working, but I wanted to double check the updates/upgrades. So, I reran the update commands. I got an error: "Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

So, I did. And I got various errors such as:
dpkg: dependency problems prevent configuration of astroberry-server-wui:
 astroberry-server-wui depends on gpsd; however:
  Package gpsd is not configured yet.

dpkg: error processing package astroberry-server-wui (--configure):
 dependency problems - leaving unconfigured
Setting up indi-full (1.9.1) ...
dpkg: dependency problems prevent configuration of astroberry-server-sysmod:
 astroberry-server-sysmod depends on gpsd; however:
  Package gpsd is not configured yet.

dpkg: error processing package astroberry-server-sysmod (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of virtualgps:
 virtualgps depends on gpsd; however:
  Package gpsd is not configured yet.
dpkg: error processing package virtualgps (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of astroberry-server-full:
 astroberry-server-full depends on astroberry-server-wui; however:
  Package astroberry-server-wui is not configured yet.
 astroberry-server-full depends on astroberry-server-sysmod; however:
  Package astroberry-server-sysmod is not configured yet.
 astroberry-server-full depends on virtualgps; however:
  Package virtualgps is not configured yet.

It goes on a bit, and ends with this:
dpkg: error processing package astroberry-server-full (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 gpsd
 astroberry-server-wui
 astroberry-server-sysmod
 virtualgps
 astroberry-server-full
E: Sub-process /usr/bin/dpkg returned an error code (1)

I don't yet have GPS, so I would have thought it would ignore gpsd.

Anyway, that's where I am presently. If you know a quick solution...

Thanks!
 

Thank you again for the suggestion. I cloned the "working" image. Unfortunately, it behaves the same.

Sounds like a hardware problem, especially if you succeeded in cloning the „working“ sd card. Can you get other images running in a stable way? I doubt it…

I was able to clone the "working" image, but it behaved the same as the non-working image. Yes, I can run raspian (buster?) no problem. 

What I had tried was updating using a Pi Zero. It got about 97% done but then stopped responding.

I took my "working" Pi and did the same thing. It, too, got to about 97% and then started giving errors. It had to do with some stuff not already installed. Once I installed what was missing, it was happy.

This updated image works in my second Pi just fine (so far). I haven't had much chance to really test it completely with it being monsoon season and all, but I have confidence.