To fully explain the problem:
I installed Windows 10 via USB key (with its .iso on it) on a mixed new parts PC (new motherboard, new cpu, new ram, new nvme 2.0 ssd, old psu, old gpu, old desktop tower, old mouse, old keyboard, old TV).
Then, once Windows is done installing, I’ll login to a new Windows session (as admin by default), download CIS complete, install it, reboot, enter my serial key into CIS complete, then go in advanced tabs of CIS complete and chose to run Clean Endpoint. CIS will then download CCE, CCE will install, ask which type of scan I want to run (I think), then ask for reboot to scan the PC. After rebooting, Windows OS would attempt to automatically repair itself, but wouldn’t succeed (and CCE scan wouldn’t run and I couldn’t reach the user login screen to a windows session). Then, everytime I try to boot the PC, Windows fails to auto-repair itself. I could only manage to boot in recovery mode (I think its called), (which is a GUI allowing: windows to auto-repair problems preventing it from starting, has troubleshooting options, allows to boot straight to windows, offers to reboot and allows access to cmd). From that recovery mode/GUI, I tried typing commands through cmd to fix windows, commands which I dont remember, but it wouldn’t fix Windows through cmd. (Probably fixmbr, sfc scannow and dism … /restorehealth).
I tried alternatives leading to the same problem. I installed Windows 10 through usb key, logged in as admin, created a non-admin user and only used that session from there to download and update CIS complete, fully update Windows 10, then download and run CCE (Clean Endpoint), but Windows would still get corrupted after rebooting in order to have CCE scan the PC (as descrived above). Also, upon my very 1st Windows install on this new mixed parts PC, through usb key again, I did login as admin, created a non-admin user and from that new user session only I did fully update Windows, then installed safe softwares such as Steam, Origin, Battle.net and had them scan and retrieve games installation on another internal HDD and when I was done installing my PC setup, I tried running CCE with the same method as previously mentionned which resulted in corrupting Windows OS.
Also, within my last 10 Geek Buddy tickets, the 7-8 older ones are all related to this issue (with maybe more details) and are all one after the other.
I’m done running Windows MRT, Avast’s boot scan and deep scan and CIS complete full scan and everything looks fine on this installation. I’ll make an image backup of the OS during the night so tomorrow I’ll be able to test and download CCE again on the PC which experienced the issue.
Thank you for the follow up.