Fixing the “Oh no! Something has gone wrong” error message on Fedora Workstation running on Hyper-V

You might have noticed the error message after rebooting after having finished the installation during the setup phase. I noticed it too on Fedora 34.

I got the screenshot online because I did not want to go through the setup phase again but the error image was the same

Fixing the issue is relatively straightforward. The only time I faced this issue was during the setup phase.

Now like most people, I presume you too have Dynamic Memory on and are allocating only about 1GB of RAM by default.

During Setup phase, monitoring the RAM usage, I noticed that the RAM consumption was between 4–5 GB.

So a simple resolution, was to Disable Dynamic Memory (I am not sure if that was the cause but then again we are going to re-enable it later) so not much of an issue and to allocate 5 GB of memory by default.

You can allocate more memory if you want to. But allocating 5 GBs worked for me.

So I now need you to:-

1. Open Settings for your VM in Hyper-V

1. Go to Hardware
   By default Hardware will be displayed and so will all of its components
2. Then go to memory
3. Disable Dynamic Memory
4. Allocate minimum of 5 GBs of memory
5. The memory is for reasons unknown listed in MBs. So you can set it to 5120. Would be so nice if we could select it in a toggle or type in 5 GB but its not like I use it regularly so not an issue.

And then press Okay

Now continue with the setup phase.

It will ask you to set some permissions dealing with location and username and password, which you might have reached to before as well but et viola, this time the configuration will be a success and it will not crash.

But Dynamic Memory is useful

Which is why we are going to shut down our VM and enable it again.

1. Shut down the VM
2. Go to the same page
3. Change the default to a lower value if you prefer
4. Enable Dynamic Memory
5. Reboot
6. It now works
7. Profit!!!!

This bug is a bit weird because while the setup faces issues running with Dynamic Memory enabled which increases the memory allocated as we go along, the rest of the OS after the setup finishes works just fine.

I tried to cause this issue by allocating only 1 GB of RAM with Dynamic Memory disabled and then trying to run the OS. While I couldn’t for obvious reasons run Firefox browser (my hope was that running it might help cause a crash of the entire OS like before), but I had no crashes. Hope it gets resolved.

I resolved it in another way

Do comment here or contact me via LinkedIn with your own resolution steps.