As you've probably realized by now, installing Fedora in BIOS/CSM/legacy mode to a computer that already had an EFI/UEFI-mode Windows installation was a mistake. My page on the CSM describes some of the problems that this type of configuration can create. Thus, one of your goals should be to either re-install Fedora in EFI mode or convert the existing installation to boot in EFI mode. Fortunately, converting Fedora to boot in EFI mode is relatively straightforward; you need only install an EFI-mode boot loader. Ubuntu users often turn to the Boot Repair tool, but I don't know how well it would cope with Fedora. Alternatively, you could install an EFI-mode GRUB, or some other EFI-mode boot loader, manually. See my page on EFI boot loaders for Linux for a (somewhat old) rundown of what's available. My own rEFInd boot manager is likely to be fairly easy to install -- you can use the USB flash drive or CD-R image to do a one-time boot and then install the RPM in Fedora. One caveat about rEFInd is that you need to jump through some extra hoops to get it working with Secure Boot enabled.
Your bigger problem, though, seems to be your inability to boot Windows. You wrote:
When I change the BIOS, which I am able to access somehow, to UEFI, it is mentioning that no disk was found, and hence I cannot boot windows.
Technically, you have UEFI firmware, not BIOS. Many people, and even manufacturers, apply the term "BIOS" to EFI/UEFI firmware, but in my experience this just creates confusion; EFI is very different from BIOS in how it boots the computer, so calling an EFI a BIOS leads people to drag in BIOS assumptions that lead to trouble when applied to EFIs.
That said, your claim that "it is mentioning that no disk was found" is vague. It would be helpful to see a screen shot (a digital photo is fine) of this error message so that we can see the exact wording, fonts, etc., all of which can provide clues about what's producing this message -- the firmware, a boot loader (and which one), a Windows component, etc.
My suspicion is that you haven't completely reversed the changes you made to the firmware. Two specific thoughts on this occur to me:
- In some cases, changing one firmware option automatically makes changes to more options, so reversing that one change may require making additional changes. Unfortunately, I can't really be sure what additional options you'd have to change.
- Windows is sensitive to the firmware's disk access method. Typical options include "AHCI," "IDE," and "RAID." If you changed this firmware option, be sure to change it back. This would not normally be changed automatically when switching from native EFI-mode booting to BIOS/CSM/legacy-boot mode, but it's conceivable that your computer is an exception to this rule.
It should also be noted that, depending on the nature of the problem with the Windows boot, it's conceivable that installing an EFI boot loader for Linux might help, since this boot loader is also likely to serve as a boot manager, which should pass control to the Windows boot loader when you tell it to. (This would help if the problem is that the firmware has "forgotten" the Windows boot entry, which might happen if you unplugged the disk or if the firmware is stupid enough to wipe the EFI-mode boot entries when you reconfigured it to boot in BIOS mode.)
EDIT: For background information to help you understand my answer, please read: