"Sorry if this question is easy" 😂😂😂 that one really cracked me up 😂😂😂😂
You don't need to be sorry, any question is welcome :)
Well, it's actually a tricky one, since (sadly) that's a really unspecific error. It can be caused by many things. Though I guess it's not a filesystem error, since the installer booted up fine. So that's one reason out.
The first thing you should check (and add to your question please) is: Where did you get the installation file (ISO/DMG) from? Is it an official distribution from the App Store, or did it come from a third-party source (a pirating website maybe?). The reason that's important is that ol' uncle Apple are extremely annoying with their security. And I mean, extremely. No access to system files on iOS type of extremely. Now that's (as always :P) a problem here, since if the installation didn't come from a first-party source (aka the App Store), then it might not be properly codesigned (I explained a bit about codesigning below). So please edit your question so it specifies the source if the installation so I can help you further.
Another reason for your problem might just be that the installation is, as specified, corrupted. What does that mean? Well, a lot of times when burning files to a disk (e.g. burning an ISO to a USB drive), there might be a tiny error (maybe even a single corrupted byte) that will just ruin the structure of the whole file. Annoying, isn't it? This can be caused by many reasons. Maybe your file is bad, maybe your disk is bad, maybe your disk maker is bad (in which case I really suggest you try a personal favorite of mine called Rufus, which is also completely free, though sadly it's only available for Windows, so try to get your hands on one for a few minutes), and maybe it just happened randomly (yep, that happens. Bummer.). Go through option one, then if you have a legit, official copy of the installer, check your disk, then just try to burn the installer again. If it still doesn't work, switch to a different disk maker application.
Codesigning
So codesigning (code-signing) is pretty much a standard when it comes to Apple systems (macOS/OS X, iOS, etc.). It's something that is really awesome but also really annoying at the same time. From Wikipedia:
Code signing is the process of digitally signing executables and scripts to confirm the software author and guarantee that the code has not been altered or corrupted since it was signed. The process employs the use of a cryptographic hash to validate authenticity and integrity.
So, as I said, it's a pretty neat idea. It's basically a little encrypted string embedded in the software code, that approves that this is the official code, from the official developer, and that it should run just like it's supposed (assuming you meet the system requirements). You can think of it just like a signature: When you see the author's signature on a document, you can be sure that it's his, and that it's original and official. And just like a signature, it's unique and hard to fake. But the problem is that it causes a lot of trouble when a developer doesn't properly sign his code. For example, I tried to use GDB (the GNU Debugger) the other day, and it didn't work due to inappropriate codesigning. Even though, for the most part, it's up to the developer to be responsible for properly signing his code, it's still pretty important to understand what it is, at least in a general, basic level.
