-
I've had this problem before, they say it's a virus, I'm not, it's deleting, disabling a system file, it seems to be C: Windows System32, or something related to this, I'm restoring, if you have a disc you boot from the optical drive, and then copy those files over.
-
Brother, you didn't see it clearly, when the recovery disk that comes with the HP system is recovered, the partition of the entire hard disk is redivided, this function will definitely be there, but there is another option is not to repartition, only restore the system disk (C disk), that's for sure! Good luck!
-
I'll keep the tutorial for you. No, just look at it.
If it doesn't work. Direct Chinese version of the disk system.
It's not a bother, and if you're dizzy, there's no other way.
If you can get into the system.
You use this and just install it when you're done.
-
Change the properties back in safe mode.
Don't think about it under DOS, because you are an NTFS partition.
If you don't know the original attributes, I advise you to redo the system, because it is a waste of time.
-
The system administrator you disabled is not the administrator
If not, recover in safe mode, and if so, don't waste time and redo the system!
-
Reinstall the operating system using the system disk.
-
Can't even enter safe mode? Wouldn't it be OK if I could go into safe mode?
Enter safe mode and change the modification permissions back.
-
Press F8 when you boot up, An, the last correct configuration,, have you tried.
-
Reset its properties under DOS.
Display or change file properties.
attrib [+r | r] [a | a ] s | s] [h | h] [drive:] path] filename] [/s [
d]] to set the properties.
Clear the attributes. r read-only file attributes.
a Archive file attributes.
s system file attributes.
h Hide file attributes.
drive:][path][filename] specifies the file properties to be processed.
s processes matching files in the current folder and its subfolders.
d also handles folders.
-
Change the icon to the smallest folder with no thumbnails, and there won't be that kind of situation.
-
Try it in safe mode, or use a file shredder to erase the file.
-
You are in the tool options,Show system files and hidden files,Then you see if each disk wants an autorun thing,Move him to the ** station first,Then restart it to take a look。
Or maybe it's because you have installed some incompatible software. Some software is embedded in the explorer, which is the explorer. Just uninstall the relevant software you recently installed, or find a compatible version and install it.
-
Use the 360 First Aid Kit to detect if the system files are infected.
-
When you install an application and it causes Windows to crash, it is likely that the application has overwritten key Windows system files, causing the system to crash. After a file has been modified, the results are often unpredictable. The system may be working normally, or something goes wrong, or it crashes completely.
Fortunately, Windows 2000, XP, and Server 2003 have implemented a mechanism called Windows File Protection (WFP), which prevents critical system files from being overwritten. One thing worth noting about WFP is that it is very closely integrated with the Windows installer. Whenever the Windows installer needs to install a protected file, it gives it to WFP instead of trying to install it itself.
It is then up to WFP to determine whether the installation is allowed.
So unless there are special circumstances, Windows File Protection should not be set to disabled.
-
Whether it is adsl dial-up or routing to surf the Internet, make it clear. Set a fixed IP address.
-
I have had such a problem on my computer before, and I can't find minidump after the blue screen, just change a memory module, it's generally a conflict of software, and the hardware is very little, so it is recommended to change an antivirus software.
-
Check to see if there is a key that doesn't pop up when you press it?
Turn off automatic updates:
Right-click on My Computer - Open System Properties - Auto-Update tab - Check "Turn off Auto-Update" - OK!
-
Restore the system to before the problem occurred.
-
NTFS has no limit, but small files occupy a minimum cluster size, so the actual space occupied is larger than the actual file size, and a large number of files is easy to cause slow access and disk waste. If you have frequent access, it is recommended to use a cache, such as Redis.
-
Visual inspection did not cause this.