A Strange "c" File with No Extension Keeps Appearing After Deletion but Not After Renaming It

Bree · Jan 7, 2025

bn40400 said:
Bree had mentioned they had it too. @Bree - Thank you for welcoming me, but did you open your copy with notepad? Was there any containing text? Just an odd file, and at this point I'm thinking it's just a harmless file maybe placed by MS for some reason or another...

Yes, I opened it. Same as yours, just the single character: \

The appdata folder is on the C: drive. In a command prompt, if you type cd \ it takes you to the root of the C: drive, the name of the file is 'C', perhaps all it is is a pointer to the root of the drive that it's on?

Ghot · Jan 7, 2025

I don't have it.

bn40400 · Jan 8, 2025

@Bree (and everyone else) Okay, so here's what I think, now I may be wrong, but I'm pretty sure this is a "marker" file from MS of who's going to get the next features installed whether it be immediately or "down the road" as they describe that some features will be turned off or on for some users who receive this update. I restored a backup of the file that I created a few days ago (trust me, I had this file incredibly protected and locked from attempting to activate should it try). So, as it appears, after the new Cumulative Update for 23H2 (at least for my setup) I haven't received any new features as was described in the OS Build 22635.4660 - since I deleted the "c" file. So, I restored the file and it NOW appears I have all of the new features that are included in this updated build. I believe this file is intended for those who gets the new features as described in the release notes - so leave this file be; as I now have the text located under the icons cut/copy/paste/delete. I think I figured it out, so I'm going to mark this post as RESOLVED.

bn40400 · Jan 8, 2025

So, for all those looking into this thread, I think I'm going to mark this post as RESOLVED. because as I previously mentioned in this thread - I came to the conclusion and am almost certain that this mysterious "c" file is a "marker" from MS, for who will receive the new features in latter builds/ cumulative updates. There is sufficient evidence (at least on my part) to prove that new features are dependent on this file that appears to be "hidden" from average users - as this file location is normally defaulted to being hidden and potentially blocked from your "average" user. Yes, it could've been pure coincidence that upon my research and discovery that MS just "decided" to allow the feature, but I'm speculating that this is a direct result restoring this file back to it's proper location. Upon restoration of the file, and a sudden crash (GSOD) these new features became apparent after a reboot. So, please leave this file be and lie where it is should it be on your system.

bn40400 · Jan 8, 2025

Bree said:
I wonder what it's for? Even Copilot is puzzled.....

And, yes I would like to thank you @Bree as you were questioning Copilot that appeared to be just about correct even though it was puzzled by the file. Thanks again for your help and time!

antspants · Jan 8, 2025

bn40400 said:
So, please leave this file be and lie where it is should it be on your system.

It was a hidden system file, leaving it alone would of been my first conclusion.
A file named C with no file extension and the content consisting of “\” would appear to me to be a root path. Perhaps obviuously related to a system process or dregs from the swap file perhaps.

But yeah, one would think there would be more info on it.

kelper · Jan 8, 2025

That's very unlikely when MS could just use a registry entry.

kelper · Jan 8, 2025

I wonder if it is related to two empty folders also called c which are owned by Network Services?

Kees · Jan 8, 2025

I don't have that 'c' file either in my user\appdata\roaming folder either.
Started the different versions of Windows 11 in my VirtualBox envirenment and no, there is no file c to find.

It must be some app, which some of us use, that left this file.

TraderGary · Jan 8, 2025

I don't have that 'c' file in my user\appdata\roaming folder either.

I decided to do a fresh clean install to start the new year, so my system is about as vanilla as you can get.

antspants · Jan 8, 2025

Kees said:
I don't have that 'c' file either in my user\appdata\roaming folder either.
Started the different versions of Windows 11 in my VirtualBox envirenment and no, there is no file c to find.

It must be some app, which some of us use, that left this file.

Not sure if I can think of many or any apps that create hidden system files on the root of C Drive, or anywhere.

antspants · Jan 8, 2025

OH, I reread the post. I think I am confusing another thread. I was sure I read that this was only visible when showing hidden system files. my mistake.

LesFerch · Jan 8, 2025

Bree said:
The one in Roaming is just 1 byte. Mine was created in November 2023, so it's been there a long time.

Have you tried searching your drive for other files with the same modified and/or created date?

BrianInEngland · Jan 8, 2025

I don't have this file

starchase · Jan 8, 2025

bn40400 said:
@Bree (and everyone else) Okay, so here's what I think, now I may be wrong, but I'm pretty sure this is a "marker" file from MS of who's going to get the next features installed whether it be immediately or "down the road" as they describe that some features will be turned off or on for some users who receive this update. I restored a backup of the file that I created a few days ago (trust me, I had this file incredibly protected and locked from attempting to activate should it try). So, as it appears, after the new Cumulative Update for 23H2 (at least for my setup) I haven't received any new features as was described in the OS Build 22635.4660 - since I deleted the "c" file. So, I restored the file and it NOW appears I have all of the new features that are included in this updated build. I believe this file is intended for those who gets the new features as described in the release notes - so leave this file be; as I now have the text located under the icons cut/copy/paste/delete. I think I figured it out, so I'm going to mark this post as RESOLVED.

So if those of us with updated 24H2 systems want the "new features as described in the release notes" but don't have the C marker we should just create the file with the "\" and we'll get them?

LesFerch · Jan 8, 2025

starchase said:
So if those of us with updated 24H2 systems want the "new features as described in the release notes" but don't have the C marker we should just create the file with the "\" and we'll get them?

I wouldn't jump to that conclusion. No harm in trying, but I expect nothing will come of it. The file may originate from some, as yet unidentified, third party software.

Ed Tittel · Jan 8, 2025

I don't see it on any of my PCs or VMs (about 2 dozen in all). Bizarre and mysterious.
--Ed--

Bree · Jan 8, 2025

LesFerch said:
Have you tried searching your drive for other files with the same modified and/or created date?

I have now. Two .xml files in C:\Windows\Panther\NewOs\Panther were created on the last modified date for the ...appdata\roaming\c file.

They have identical contents.

Code:

<WINDLP>
<State>0</State>
<TaskCount>0</TaskCount>
<WorkingPath>C:\$Windows.~WS\Sources\Panther</WorkingPath>
<StringCount>0</StringCount>
<DwordCount>0</DwordCount>
<QuadwordCount>0</QuadwordCount>
</WINDLP>

bn40400 · Jan 8, 2025

@Bree and others.....So, as I was viewing the same .xml files and the containing folder - It appears to be a setup of of a windows update and media creation tool. I've opened the .xml files, and they all point to Windows store upgrades as well as the main Windows update installations. I've took some screen snippets of the containing text in these files. Please, have a look. So, at this point, I am convinced that this is some type of Windows component update for sure - especially after restoring the original file back (after a crash of course that involved netios.sys which caused a GSOD), I have the newer features immediately available after a reboot that followed the crash. Currently I'm looking for additional logs and perhaps a dump file to verify if that "c" file is part of windows update.

bn40400 · Jan 8, 2025

Bree said:
I have now. Two .xml files in C:\Windows\Panther\NewOs\Panther were created on the last modified date for the ...appdata\roaming\c file.

So, I can't find any dump files in the minidump folder or the main windows C:. I did run a windows update log, but I cannot find anything about the C:\Users\<username>\AppData\Roaming directory. However, in the log, you can see when the crash occurred when I restored that "c" file - which was at 9:13 PM. Communications with the WU service seemed to cease at 9:01 PM prior to when I had the crash. The log shows that the WU service did not reinitialize until 9:27 PM, which was when I discovered that the new features were available shortly thereafter. May be just coincidence, however, I can't seem to link the modification dates of those xml files to my restored "c" file on my PC as I was messing around with darn file for quite a few days, and when I restored it, it changed the modified date of the file to the current date and time which was yesterday. The .xml files have a modification date of 1/5/25 1:56 PM. So, maybe we're back to square one again about the origin of the file, I'm thinking?

A Strange "c" File with No Extension Keeps Appearing After Deletion but Not After Renaming It

Well-known member

My Computers

Well-known member

My Computers

Active member

Attachments

My Computer

Active member

My Computer

Active member

My Computer

Like a rolling drone.

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Stock Market Wizard

My Computer

Like a rolling drone.

My Computers

Like a rolling drone.

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Active member

Attachments

My Computer

Active member

Attachments

My Computer

Similar threads