I startup an Executable File (it doesn't matter whether is a program or an Installer) on an NTLited Windows and get that and a force close as a result. I didn't change my preset at all, only integrated the latest updates. Any clues why? Sometimes they open just fine the first time, but trying a second time (obviously, not the installer files) gets me the error.
Constant 0xc0000005 Errors (Floxit.E virus)
- Thread starter PhsMu
- Start date
- Status
Try keeping Error Reporting, when kept those errors are invisible to the user, it's not caused by the removal.
But the Error Reporting API should be the component protecting the needing pieces, do you have that component listed and kept or is it only Error Reporting on the full ISO (non-API)?
But the Error Reporting API should be the component protecting the needing pieces, do you have that component listed and kept or is it only Error Reporting on the full ISO (non-API)?
Will try!
Error Reporting API is kept, and Report is removed. Trying Keeping both.
nuhi: The issue apparently stems from NTLite being infected by a Floxit.E virus, and injecting it into the images. I don't know where it came from, but I had to install the whole system on a default image and redownload everything and redo the image to avoid the problem. Let's try with the image and see if it solves the issue.
Error Reporting API is kept, and Report is removed. Trying Keeping both.
nuhi: The issue apparently stems from NTLite being infected by a Floxit.E virus, and injecting it into the images. I don't know where it came from, but I had to install the whole system on a default image and redownload everything and redo the image to avoid the problem. Let's try with the image and see if it solves the issue.
Last edited:
Eh it seems you misunderstood me. Its a general warning from (a very bad) experience that if you get the malware, you have to ntlite your image elsewhere or the image will still contain the malware. NTLite itself is not infected, but transmits the infection, if you get it elsewhere.
Hellbovine
Well-Known Member
Just download a fresh iso from microsoft, mount it and install a fresh windows. Then with a clean install download ntlite fresh (don't use any previous files) and activate, then make your image.
You're just going to deal with more time lost doing it any other way.
You're just going to deal with more time lost doing it any other way.
Yeah, I kinda noticed that, problem being the 16tb HDD attached to my device I have to scan. I have things in there I don't believe I can find again, including some older but much better versions of some software in the market. Or non-DCH Intel UHD Drivers from Dell.
Windows 10 User (again3)
aka Malaria, you never get rid of it.
Could you tell me how did you fix this problem? I'm having it too.
Windows 10 User (again3)
aka Malaria, you never get rid of it.
Why do you think that? According to what I searched, supposedly it really is an infection issue.
Windows 10 User (again3)
aka Malaria, you never get rid of it.
I have this problem with many apps and none of them run with compatibility mode. According to what I searched, the culprit is really this Virus.Floxif.
OK, my solution was to install linux, disinfect all my files with ClamAV, losing quite some stuff in the process, then reinstalling everything back. Any other attempts to disinfect windows got me bluescreens and plugging the external drives to check them infected the machines before I could even start the anti viruses.
Windows 10 User (again3)
aka Malaria, you never get rid of it.
Already did, many times. I still have this virus, somehow.
I never installed Linux. So, you installed Linux, installed ClamAV in it to search for virus in the infected partition and then reinstalled everything back in the previously infected partition?
Try Linux Mint, its the easiest of all in my opinion.
No, I backed everything up to an external HDD, COMPLETELY ERASED THE DISK, REPARTITIONED, installed linux, scanned all the files (took me WEEKS) and deleted the infected ones. then I reinstalled windows (default), and without internet access, installed ntlite and recreated my image then reinstalled the PC into useable state.
Windows 10 User (again3)
aka Malaria, you never get rid of it.
Well, I hope the external HDD isn't infected or I'll have this issue again after connecting to the PC, I guess...
crypticus
Well-Known Member
IDK if it would work but I would just upload all my important files to a cloud. and format my system. then download not infected ones. even google drive scans for files and warns you if its infected... you will lose too much data but you will lose them anyways...
also starting system with linux to go usb or security iso would be same too
also starting system with linux to go usb or security iso would be same too
Windows 10 User (again3)
aka Malaria, you never get rid of it.
I forgot to say but my PC only detects the USB device where I burned the Windows 11 installer ISO at the second time, i.e., after trying to boot from the USB, nothing shows up in the boot list's USB section, so I choose to boot from the HDD, then press CTRL + ALT + DEL to restart the PC and then the USB device shows up in the boot liat. I don't have this problem with other USB devices with other programs but I do if I burn the Windows 11 installer to them. I don't have this problem in other PCs with the same USB devices and Windows 11 installer image I'm having in this PC. What can be the cause of this problem?
Last edited:
Windows 10 User (again3)
aka Malaria, you never get rid of it.
It looks like the culprit is a Visual Basic Runtime 5.0 installer that according to VirusTotal has the mentioned Virus.Floxif. I did another clean install, downloaded and installed another Visual Basic Runtime 5.0 and I stopped having this problem. I needed that program to be able to run another and I wasn't even remembering I was running it every time I installed Windows. What's weird is that I still have that error message when running a specific program but other ones are fine.
- Status