You are exaggerating the scope of the possible issues a bit.
fix system files and MFT
Defraggers don't usually do that
frag can freeze games, slow a PC down to a crawl, take an hour(s) to load Win10
Yes but only after long excessive usage on a very full disc
prevent downloading when there should be enough space
No, fragmentation cannot cause that.
the one built into Windows is a demo
It works well since win 7 for it's main purpose of keeping up reading speeds at a proper level. It does not do advanced repositioning of files to minimise further fragmentation but that is an extra that most don't need.
Comment has been collapsed.
pointless detraction, but thank you for acknowledging the superiority of the 2 defraggers I suggested and use
Those 2 defraggers don't do that either. What they do is defragging system files and MFT, they don't fix anything,
defragging stopped sudden framedrops in Frostpunk and apps freezing on my 1TB, with 250Gb used, two days ago
If defragging fixed apps freezing then the problem is your HD is dying and the defrag just moved stuff from damaged sectors (not completely bad, but damaged enough so the HDD need to retry several times to be able to read) to working ones.
downloads fail in the last moment of finishing if insufficient contiguous freespace, the error message states it
I fixed a PC last week that got this problem from 6mos of Win10 updates, it also had all the other problems I mentioned
all it needed was a proper full defrag. only half the drive capacity was used btw, and it looked like the files exploded
Can you show the actual error message? I don't know of any file system (even good old FAT32) that has such limitation. Are you sure the error was referring to HDD and not RAM (this can happen with RAM, since memory allocations must be contiguous there)?
Comment has been collapsed.
"fix system files" means what it means. Use proper language if you want people to understand you.
It's not nitpicking, you're trying to help someone with bad info, missguiding him. HDD fragmentation doesn't provoke the problems you're describing. It has an IO performance impact, but not nearly as severe as you describe, specially in modern file systems. Starting with Windows 7, there's already a weekly schedulled defrag by default, and yes the Windows built-in defragger (starting with Windows 7, the ones in older versions were crap) is good enough for any normal user. I don't know where did you get the idea that it only defrags prefetch files, but that's not true at all.
You say defragging fixed the problems you describe? Well, that's probably because all defrag tools out there do a filesystem check before doing the defrag (chkdsk /f or maybe a built-in tool), and that's what actually fixed your stuff.
Comment has been collapsed.
outdated is not the same as bad or misguiding
But your info wasn't outdated: it was never true. No version of defrag does what you said. In any case, outdated info is as bad as invalid info. Both are incorrect today
you've just never encountered such and I have multiple times
I've never said it's the only cause or the only remedy, just that it "can", "may" and "might", and when questioned I gave examples
The problem is not really that you suggested a defrag (it's really not a bad thing to do), but you suggested to buy some unneeded commercial software and mentioned certain malfunctions as caused by disk fragmentation when it can't cause those and in no circumstance data needs to be contiguous in the filesystem (there's not even any kind of Windows API call to request contiguous disk space, ans this is why I still think you misunderstood that error message).
A fragmented filesystem can't provoke issues other that degraded performance. Anything else is some corruption in the filesystem (and modern filesystems, including NTFS, have a lot of redundancy so a simple tool like chkdsk can fix those issues easily). So defraging can fix those problems? yes and no: the defrag itself doesn't, but since it is usual to perform a filesystem check prior to the defrag, that will fix those issues. But you can just do the check alone and not wasting time with an unneeded defrag.
modern? NTFS was released in 1993 Win3.1NT, the latest release v3.1 in 2001 XP, oh and btw
Modern doesn't mean new. NTFS has been updated and improved over the years. It has the general design and features of any other current filesystem. The versioning can be a bit misleading since Microsoft stopped caring about changing the version number, but new features have been added since the XP version (Vista, for example, added symbolic links, as a filesystem feature, not just an OS feature), and also performance and reliability improvements.
and btw
English is not my native language, and in Spanish we have a single word for both of those, so it get's difficult to differentiate when to use each. I generally don't even acknowledge 'especially' as correct English, that word looks weird to me :P. Thanks for the correction.
Comment has been collapsed.
What I said: you probably misunderstood the error message
What you undertand: You're calling me liar!
O...K...
Believe me, I googled it to try to figure out what error message you may have gotten (since for whatever reason you don't want to say it). All I've found refer to RAM, none to file systems (some refer to HDD partitioning, but that's not what we're discussing here).
I stated where it came from. claiming it didn't exist because you weren't aware of it is stupidity in action and insulting.
I don't even know what you're talking about here...
because you're voluntarily ignorant
You say that but you fail to explain why the problems you describe would be fixed by a defrag. "My experience says so" is all I've read from you, but CS is not an empirical science. I've tried to explain why you may have had the impression that defrag fixed the problems, but you ignore that. So who's the voluntary ignorant?
A bit childish to block me because of a discussion.
Comment has been collapsed.
GUYS!!! I made a edit, go read it, I found out that was a main problem actually, now I need a maximal help from u and don't make any kind of debate, discuss good, be good, help, and everyone should be fine :D
thanks again everyone for helping
Comment has been collapsed.
Does this happen only with Stanley Parable, or also with other games? And what do you mean by "just started to install"? Did it do the memory allocation thing and the download already started? Or does it really happen the second you click on install?
Comment has been collapsed.
I still don't understand. Does the installation turn off, so that the game doesn't get installed but Steam is still running? Or is Steam shutting down?
Check the event viewer for errors and warnings. Tell us if you find anything there.
Comment has been collapsed.
Installation stops, goes on Paused, on the quene in the Steam download managment, and then 2 seconds after that, Steam shuts down, and then trying to turn on, it turns on, but then hey in Steam download managment that game just started with installation and after 2 damn seconds it shuts down! And nah I didn't found out anything yet...
Comment has been collapsed.
When you say "it just turns off" do you mean Steam shuts down, or that your entire computer immediately loses power? As in, it doesn't initiate a shutdown and then shut off, but instead its a hard power cut like if you pulled out the power plug? Does the computer restart after this, or do you need to press the power button on your computer to turn it back on?
Comment has been collapsed.
If Steam is the only thing that closes (including the Steam icon disappearing from the tray next to the clock), then you should contact Steam support for assistance. Steam does have logs and dumps folders located in the C:\Program Files (x86)\Steam\ directory that may not reveal much useful info to you, but could be of use to Steam support in figuring out the problem.
Comment has been collapsed.
Which win version do you use and are there any errors listed in the Log viewer?
what does debug.log in steam's folder say?
Do you have uplay,origin,epic and can try to load a game there to see if it works?
Comment has been collapsed.
Im using windows 7, I didn't saw anything related to debug.log but I saw some files appears when I try to start Steam
.crash
and some ssfn103617 and something, now another same ssfn but different number ''ssfn62060014654443503''
And yeah I got a Battle.net but I don't really think the other app is the problem
Comment has been collapsed.
And yeah I got a Battle.net but I don't really think the other app is the problem
Point is to make sure your PC is not at fault here, so when other clients work, we can save suggesting all various PC related fixes and focus on steam.
Also IBC made an excellent point: it could be some stuff linked to your profile.
You can make a new Steam account and try to download any free game on a fresh install and see if that works. Then we will know for sure that some workshop item causes the issue.
Comment has been collapsed.
Had a similar issue with steam, was able to pinpoint that steam tried to update a some no longer available workshop content for Cities: Skylines. So make a not of which games you tried to install and try to unsub to all of the workshop content from one by one and see if the issue persists. if yes than it seems to be an internal problem (memory allocation, page-file intrusion etc...)
Comment has been collapsed.
My issue started up back when they started removing workshop entries due to reuploads that the logs treated as an invalid entry and from what I could see that the logs stopped at that specific entry and every time I tried to find it it wouldn't show up in the workshop. Only was able to clear it out with the unsub to all function after uninstalling the game.
Comment has been collapsed.
Try installing on a different drive, if you have one.
Comment has been collapsed.
If I make something on disk C, then install something connected to that in disk D, that app will constantly for I don't know what reason drain the space in disk (mostly C), heard that from my friends and I experienced that hell... Now to try that again I don't want to risk
Comment has been collapsed.
I meant try installing on a different storage device, so you can know if this is a hardware issue or not.
Comment has been collapsed.
download on a new disk. or reformat the disk??
works for me
Comment has been collapsed.
Read through these:
Try this one:
https://steamcommunity.com/discussions/forum/1/2217311444334406020/#c1458455461472154996
Comment has been collapsed.
7 Comments - Last post 48 minutes ago by SlavenHarkin
5 Comments - Last post 49 minutes ago by iubjaved
352 Comments - Last post 1 hour ago by ChrisKutcher
3,111 Comments - Last post 1 hour ago by meruleron
16 Comments - Last post 3 hours ago by Comiclove
2,038 Comments - Last post 8 hours ago by LordDarkness
551 Comments - Last post 12 hours ago by Warriot
445 Comments - Last post 9 minutes ago by mijamal7
645 Comments - Last post 37 minutes ago by BHTrellis188
201 Comments - Last post 44 minutes ago by gienek
2,372 Comments - Last post 2 hours ago by Zipsy
143 Comments - Last post 2 hours ago by Catlord
49 Comments - Last post 2 hours ago by SquishedPotatoe
53 Comments - Last post 2 hours ago by Lugum
Hello guys I have some issues with the Steam app, so this is how it all started:
EDIT ! ! !
EDIT 2
Comment has been collapsed.