1) Any Windows PE-based pendrive/DVD should provide you with a somewhat limited Windows environment that allows you to edit files from the broken Windows installation on your hard disk. Don't think these are free. But sure are the most convenient.
2) You can also download a Linux distribution iso. Burn that to pendrive/dvd and boot the problematic computer from that. In the setup routine there is always an option to "test drive" the distribution from pendrive/dvd. Select that option and mount the hard disk from the problematic computer. Then try and edit the broken content in files using Linux tools. Most distributions know how to handle files stored on NTFS based partitions and FAT32 partitions by default.
3) If you had previously installed software like AnyDesk/NoMachine/DWService on this PC (as a background service) you would have had the option to access files on your hard disk from a remote computer (in your LAN or through the internet). This is not a very safe solution, but in principle it works for editing files.
4) Is your computer part of an Active Directory setup?
If yes, please ask the administrator to fix the problem for you.
If not, what were you thinking? Now you have set yourself up for a big failure and most likely a re-install of Windows.
5) There is another way and it leads through a legally gray area:
You can use either your own Windows installation media, the Windows PE or Linux pendrive/dvd to boot the problematic computer. If you don't have your Windows installation media at hand, there are many detailed instructions on how to do this (for free) using the Microsoft website and tools.
If you chose to boot from Windows PE or Linux, use the file navigator to access folder: Windows -> System32 rename 'login.exe' to 'login.original.exe', then copy 'cmd.exe' to 'login.exe'. Reboot the computer. After the reboot finishes, you end it in a DOS prompt. You can now start msconfig using the command line and undo whatever you did previously. When done, delete 'login.exe', rename 'login.original.exe' to 'login.exe' and reboot the computer. You should now have your login screen back. If you don't, there is likely an ACL (Access Control List) mishap going on in your system. You'll need to redo the steps from this paragraph and troubleshoot any ACL mishap from the command-line. Not nice at all, but that is what you'll have to do. Can take a minute, can take the whole day. Your guess is as good as mine.
If you chose to boot from your Windows installation media, you can start the installation procedure and at the first step, hit keys: <SHIFT> + <F10>. You will get a command prompt, where you can to access folder: Windows -> System32 rename 'login.exe' to 'login.original.exe', then copy 'cmd.exe' to 'login.exe'. If you can't, the first thing to check is to see if the command line window has been executed as administrator or not. And if it did start as Administrator and you still can't copy/rename files, there is most likely an ACL (Access Control List) mishap going on in your system. Well, have fun fixing those. Again, this can take a minute, but also the whole day. Anyone's guess.
On a side note:
Why did you conclude that it is a good idea to disable all (background) services from Windows/Microsoft? These services are there for a reason. Most, if not all, very necessary for Windows to function at all.
