Try holding down the left Shift Key at boot up in order to pull up the Recovery Menu.
When you see the recovery menu, arrow key down to the "Drop To Prompt" option.
Hit enter to proceed, then manually remove the extension with:
rm ~/.local/share/gnome-shell/extensions/tilingnome
Once done, back to the recovery menu and select to Resume Boot.
Please update this thread if successful or if unsuccessful.
Tried this and it said "rm: cannot remove '/root/.local//share/gnome-shell/extension/tilingnome': No suck file or directory"
Ok please try the following. Replace $USER with your actual user name on your computer:
rm /home/$USER/.local/share/gnome-shell/extensions/tilingnome
Again, it says no such file or directory.
Might just format my drive and install a different distro with cinnamon/xfce if there are no other solutions.
One of the more useful terminal commands is locate.
let's try that in your Recovery Prompt:
locate tilingnome
If the output shows the location, you can alter the rm command above to use that path, instead.
No need to do so if you want to. You can install XFCE desktop with:
sudo apt install xfce4
Once installed, you may then be able to log in on the XFCE desktop and manage the tilinggnome extension using a GUI method that is more familiar to you.
If you prefer Cinnamon:
sudo apt install cinnamon
For Basic Desktop:
sudo apt install cinnamon-core
For fuller and configured desktop:
sudo apt install cinnamon-desktop-environment
Before you go that extreme, you could boot your system with a Live USB and try to delete this offending file externally. GNOME extensions should be located in your home directory - means not that difficult to remove.
I did not think of that... Very glad others are on here to add their brains.
Zorin OS Lite (XFCE) is an option (for extremes 
)
I have been doing "locate tilingnome" and it simply did nothing. It's like t the command doesn't work or the file doesn't exist.
I will attempt this method tommorow, it's getting late here in Australia.
We'll be here. Don't sweat it, I am sure we can get you fixed up.
Thanks, luckily I have all my files backed up on Google drive if all else fales.
I forgot to mention.
If you use Zorin Lite with XFCE desktop, tiling function is natively included. No need for an additional extension.
So I have created a bootable USB with Zorin Lite and am currently in the home folder. I'm guessing ai have to go into the .local folder but when I try go into says "permission denied"...
In terminal type
sudo -i
When it elevates to root, type
thunar
to open the file manager with root elevation - this should allow you access to the files.
Ok, thank you so much guys, it worked!
Great - what was the actual location of the Tiling Extension? (For future reference)
home/$USER/.local/share/gnome-shell/extensions/tilingnome
You can also enable "open folder as a root" function in options of Thunar. No terminal command required.
I just wanted to add one comment.
An incident like this makes me think twice before installing any extension in Gnome. One reason I choose Zorin is that its design is (almost) perfect for me and I do not have to do much customisation of my own.
For me, XFCE is a better playground for user customization than Gnome.
I would go so far as to say that Zorin 16 took great strides toward making Gnome Shell far more tolerable than I have ever seen Gnome be. It did so... using certain gnome-extensions...
I still will not use Gnome. But I think it is a great bit of work by the ZorinGroup, as it restores some much needed control to the user helping a person shifting from MS to Linux. It presents enough user control to entice the user to want more.
I am very wary of Gnome-Extensions. Most are quite good and well developed - that is not really where the problem is. The problem is in Gnome_Shell. It easily corrupts extensions that should work.
This is why merely reinstalling a gnome-extension works often - because it was not the extension itself that was flawed.
But I remain wary in general since Gnome-extensions allow a security gap- that any extension can easily insert foreign code on your working build.
Most are quite good... Some are most definitely not.