Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
It wrote something and when verifying the write, it got something else back
Inspect your disk health / SMART stats using a tool like crystaldiskinfo or something. Likely you need to replace your SSD.
It is only in rare cases that Corrupt Disk is a bug; just saying that up front.
HOLD DOWN WINDOWS KEY + R, TYPE CMD
DOS OPENED, TYPE CHKDSK /f .... still problem?
CHKDSK /f /r
the disk may be locked by another process.
You have to invoke this utility running in elevated mode
and make sure the disk is unlocked.
This is what i get when i type it
You need to run that command as admin.
I recommend the following launch method. Windows Key + X. (this is the same as shift right clicking the start button (windows logo button in your task bar) )
you will see "Terminal (Admin)" listed there. click that
then say Yes on the UAC prompt.
This will open up Powershell on windows 11 (by default at least). You can use powershell to achieve the same things, since powershell still supports cmd applets.
so just type chkdsk /f there and it should work.
check disk only fixes the file system and moves stuff away from corrupted sectors; its more effective on hard disk drives with solving issues. The problem is that likely you have a modern system and use an SSD. Usually SSDs die quickly when they start dying.
that is why I recommend inspecting the SMART status- see the health of the disk.
Feel free to try and use chkdsk though; just a note, if this is your C:\ (system) drive, then it will be very slow and require a reboot.
---
That makes it sound as if it was a bug.
Do you know what that tool did exactly or what went wrong or why it didn't work?
This whole philosophy of keeping everything invisible doesn't leave you with a lot.
I hope the problem stays away then.