Windows 7: How to stop Windows 7 from writing desktop.ini files everywhere?

It is the only solution there is. Either you hide them or you live with them in view.

Did you just do Windows Updates? That would be why.

One is in Public\Desktop the other in [Username]\Desktop, They are not in the same folder.

I've found a way to stop desktop.ini files from reappearing on the desktop, at least after one reboot. In Control Panel, click Folder Options, select View tab, and click Reset Folders, and confirm. In Advanced settings, check "Always show icons, never thumbnails", and click Apply. Then delete the desktop.ini files.

I'm still not sure whether that stops Windows from getting desktop.ini file ready to be written to CD/DVDs, or from writing them to other removable media.

I know about this feature of viewing multiple folders as one (though I forgot the actual name), but that doesn't mean I particularly like it. desktop.ini file notwithstanding, someone might have two (or more!) different files saved in multiple folders under the same name, and the aggregate folder would show all of them, leaving the user wondering which is which. I tend to do that with everything ranging from photographs (DSC_0001.JPG is one of the most common file names I have on my system, disregarding the desktop.ini) to video, to text.
Not that I know of. I tend to note when my computer gets updated.
IOW, there is no other solution, i.e. no solution that would make me happy, ergo no e-beer. Sorry.

@Sourcerer
If you have set windows to "Show hidden files" and "Hide system files", then you wont see the desktop.ini files but will still be able to see the hidden files.


That wont actually stop windows from writing the files, but atleast you wont see them

They have a more elegant solution at their fingertips - Alternate Data Streams

ADS's are not an MS idea though, only the name is theirs, ADS's are an implementation of a unix file system fork, which like most ..ix things came from Multics, which borrowed many things from Burroughs MCP. MCP was written in Algol, the precursor of many modern computer languages, Multics was written in PL/1 which bore a strong resemblance to Algol, as of course does C.

So why don't MS use ADS's for desktop.ini, thumbs db etc ?

You cant have ADS's on a FAT/32 device - so you can blame good ol' "backward compatibility".

As a s/w developer I've found if you don't retain 100% backward compatibility then 50% of users will want you hung, drawn & quartered; when you retain 100% backward compatibility then 50% of users will want you shot at dawn and buried alive - and the two groups are not necessarily mutex's.

Basically any adornment you give to a folder will probably create (or add to an existing) desktop ini file.

pjd

Don't use the built-in burner app and you won't be prompted that they are "ready"? I have never used the built-in burning app, and I have never been prompted that the desktop.ini is ready to burn. I've seen it in screenshots posted before, so I know what you are talking about, but I honestly couldn't replicate the behavior.

As for the level of tech knowledge, hiding system files has nothing to do with whether you are an expert or an end user. Since you have no reason to be mucking with those files, there's no reason to show them. Should you need them...you know how to access them.

See this page for info on this.

Desktop.ini File in Windows 7 CD/DVD RW Drive Ready To Be Written to the Disc » My Digital Life

If you scroll down the page, reader called Nemo has suggested an alternative solution.

I'm with Deacon. Why do you want to the view the hidden files at all times? They're hidden for a reason as they can pose security threats. If you need to view them, is it that hard to click 'Show hidden files'?

There are several reasons. Back before I knew about how Windows writes information on thumbnails, I had hidden files really hidden from view. Then came the Thumbs.db file which got updated in a folder whenever I viewed a thumbnail of a photo. Since I had a folder through which many photos have passed, the Thumbs.db had grown to a really huge size of several hundred MBs (which was a whole lot then) and since it was hidden I had no idea where all my disk space had gone. Moreover, when I copied a file called, say DSC_0001.JPG to that folder, and I had previously viewed a file that had the same name, the old thumbnail from Thumbs.db was loaded and displayed in Windows Explorer. Showing hidden files was then sort of a revelation for me, just as preventing Windows from writing a Thumbs.db file at all. This is why I'm always showing hidden files - because I want to know what my disk space is being used for and not just watch how my free space is decreasing inexplicably.

As for showing system files, I had a nasty encounter with a virus once and it got archived in a restore point. I had successfully removed it, but not the copy stored in a restore point. Imagine my surprise when it got back after I had restored my computer about a month later when for some reason (I don't quite remember what it was) I had to revert the system back to a previous state. After removing the virus again, I tried deleting restore points, but the interface that was made for this wouldn't remove it as it was blocked by my antivirus software because of the virus that was in it. Eventually I had to delete restore points manually (and just imagine the pain of having to give myself permissions to manually remove an infected file). On another note, restore points take up a lot of space as well, and are significant when managing a limited disk space - and mind you, with unmanaged Windows any disk space eventually becomes limited.

For these reasons I don't like to be in the dark about anything that goes on on my computer. I know enough to know what I can and what I can't remove or edit. After all, my Windows XP installation was running smoothly (with the exception of the two infections of which one was due to a restore point) for seven years without a single reinstall, which is by far more than what I can say about most installations I've seen.

Won't that prevent me from using the built-in burner?