Since when did a .jpg file become a system file? I was deleting a music
folder which contained some .jpgs of the album cover, etc., and Windows
kept asking me if I wanted to delete this system file.

As far as I know, a file with a .jpg extension has never been essential in
keeping Windows running, so why are they treated like system files?

MajorLanGod wrote:

> Since when did a .jpg file become a system file? I was deleting a
> music folder which contained some .jpgs of the album cover, etc., and
> Windows kept asking me if I wanted to delete this system file.
>
> As far as I know, a file with a .jpg extension has never been
> essential in keeping Windows running, so why are they treated like
> system files?

How did you select the file to delete it? Did you select a range of
files, or all files, to select the one file? If so, maybe you have
Explorer configured to show all files, and you included the desktop.ini
file to delete. Just something that came to mind, but I'm not sure the
desktop.ini file is considered a system file although it is used to
store folder layout, settings, type of folder, etc.

Open the folder with the file in a command shell (cmd.exe). In the
shell, run "attrib *.jpg" to list the attributes of the .jpg file. Is
the "S" (system) attribute set on the file?

MajorLanGod wrote:

> Since when did a .jpg file become a system file? I was deleting a music
> folder which contained some .jpgs of the album cover, etc., and Windows
> kept asking me if I wanted to delete this system file.
>
> As far as I know, a file with a .jpg extension has never been essential in
> keeping Windows running, so why are they treated like system files?

Since someone or something set your .jpg file's system attribute, that's
when.

Back in the old days of Windows, one could see whether a file's system
attribute was turned on by right-clicking the file and looking at the
file properties.

Windows no longer shows the file's system attribute in file properties.
It is surprising how quickly people can forget about a thing when it is
hidden from view. Microsoft has your peace of mind at heart -- without
the file's system attribute showing, surely there is now less for you to
worry about in Windows. :D

These days one can see whether a file's system attribute is turned on by
showing the attributes column in file explorer.

On 1/25/2022 11:13 PM, MajorLanGod wrote:
> Since when did a .jpg file become a system file? I was deleting a music
> folder which contained some .jpgs of the album cover, etc., and Windows
> kept asking me if I wanted to delete this system file.
>
> As far as I know, a file with a .jpg extension has never been essential in
> keeping Windows running, so why are they treated like system files?
>

Files can be marked with attributes. (An attribute is a form of
metadata, on a per-filenum basis in the file system.)

The "dir" command, has some options for displaying
materials for the first few attribute types. But
the attribute bitfields were extended to include
more than the basic file system commands normally show.

dir /ah

The following is from my notes file.

*******

File attributes can be read with (assuming user has not turned off USN!)

[as administrator... assumes file exists...]

fsutil usn readdata Y:\Windows\Logs\CBS\CBS.log

Constants - the following attribute values are returned by the GetFileAttributes function:

FILE_ATTRIBUTE_READONLY = 1 (0x1) \
FILE_ATTRIBUTE_HIDDEN = 2 (0x2) \___ file utilities work with some of these
FILE_ATTRIBUTE_SYSTEM = 4 (0x4) / as these were invented a long time ago
FILE_ATTRIBUTE_DIRECTORY = 16 (0x10)
FILE_ATTRIBUTE_ARCHIVE = 32 (0x20)
FILE_ATTRIBUTE_NORMAL = 128 (0x80)
FILE_ATTRIBUTE_TEMPORARY = 256 (0x100)
FILE_ATTRIBUTE_SPARSE_FILE = 512 (0x200)
FILE_ATTRIBUTE_REPARSE_POINT = 1024 (0x400)
FILE_ATTRIBUTE_COMPRESSED = 2048 (0x800) old style compression, icon colored
FILE_ATTRIBUTE_OFFLINE = 4096 (0x1000)
FILE_ATTRIBUTE_NOT_CONTENT_INDEXED = 8192 (0x2000)
FILE_ATTRIBUTE_ENCRYPTED = 16384 (0x4000) EFS, not bitlocker, icon colored

*******

Presumably you can assign new values, with the appropriate
piece of code to do it.

If you are downloading JPG files, there
is no particular reason for the System bit to be set. Unless
it is part of a malware, like snowstorm.jpg.scr or snowstorm.jpg.exe .
Those are examples of files the malware person wants you
to double click, where the malware person relies on the
OS hiding the extension in File Explorer by default, such that
the EXE and SCR bits can't be seen.

Setting a System bit on an item like that, I would guess somebody
wants you to be double clicking that file, when the file
simply won't delete. It's like pouring bacon fat on a trap
you've set for an animal :-)

Summary: A JPG file is not "treated" to begin with.
It does not need any attributes, to get its job done.
But you can add attributes, to change the OS behavior a bit.
I would class this as a "bad sign" (tm). Should not happen.
Just don't double click the thing, until you have thorough
vetted the file. At least do Properties on it, for a
quick look. Check the name, look for extension trick.

Paul

MajorLanGod wrote:
> Since when did a .jpg file become a system file? I was deleting a music
> folder which contained some .jpgs of the album cover, etc., and Windows
> kept asking me if I wanted to delete this system file.
>
> As far as I know, a file with a .jpg extension has never been essential in
> keeping Windows running, so why are they treated like system files?
>
It's rare that a jpg file would have 'system' properties.
- saved in a different folder inheriting that folder's or file
properities of other objects or previously manually changing are two of a
few other possibilities.

Sure it was a jpg file and not a system file in the folder(e.g. a
*desktop.ini or other *.ini file)?

--
....w¡ñ§±¤n

On Tue, 25 Jan 2022 at 23:23:30, VanguardLH <V@nguard.LH> wrote (my
responses usually follow points raised):
>MajorLanGod wrote:
>
>> Since when did a .jpg file become a system file? I was deleting a
[]
>Open the folder with the file in a command shell (cmd.exe). In the
>shell, run "attrib *.jpg" to list the attributes of the .jpg file. Is
>the "S" (system) attribute set on the file?

Or right-click on the column headings in Explorer, select More..., and
(scroll down and) tick Attributes, and look for an S there.
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"Usenet is a way of being annoyed by people you otherwise never would have met."
- John J. Kinyon

On Wed, 26 Jan 2022 at 01:01:36, Paul <nospam@needed.invalid> wrote (my
responses usually follow points raised):
[]
>Summary: A JPG file is not "treated" to begin with.
> It does not need any attributes, to get its job done.
> But you can add attributes, to change the OS behavior a bit.
> I would class this as a "bad sign" (tm). Should not happen.
> Just don't double click the thing, until you have thorough
> vetted the file. At least do Properties on it, for a
> quick look. Check the name, look for extension trick.
>
> Paul
Or open it from inside something (like IrfanView) that views .jpg files
but does not run executables (at least, I don't _think_ IrfanView
does!), rather than just double-clicking on it.
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"Usenet is a way of being annoyed by people you otherwise never would have met."
- John J. Kinyon

On 1/25/2022 9:13 PM, MajorLanGod wrote:
> Since when did a .jpg file become a system file? I was deleting a music
> folder which contained some .jpgs of the album cover, etc., and Windows
> kept asking me if I wanted to delete this system file.
>
> As far as I know, a file with a .jpg extension has never been essential in
> keeping Windows running, so why are they treated like system files?

Was this jpg the photo associated with music files in the same
directory? Was it's name folder?
--
Jeff Barnett

Jeff Barnett <jbb@notatt.com> wrote in news:sss2jb$91k$2@dont-email.me:

> On 1/25/2022 9:13 PM, MajorLanGod wrote:
>> Since when did a .jpg file become a system file? I was deleting a
>> music folder which contained some .jpgs of the album cover, etc., and
>> Windows kept asking me if I wanted to delete this system file.
>>
>> As far as I know, a file with a .jpg extension has never been
>> essential in keeping Windows running, so why are they treated like
>> system files?
>
> Was this jpg the photo associated with music files in the same
> directory? Was it's name folder?

Yes it is. I have many albums loaded to my hard drive. Usually each album
has several .jpg files showing the various covers, etc. And you guys are
right. All of the .jpg files have the H&S attributes set. God knows why,
but at least I now know what is going on. Now to figure out the best way
to go through 700+ folders and turn the System attribute off.

On Sat, 29 Jan 2022 05:38:50 GMT, MajorLanGod <lonelydad58@gmail.com>
wrote:

>Jeff Barnett <jbb@notatt.com> wrote in news:sss2jb$91k$2@dont-email.me:
>
>> On 1/25/2022 9:13 PM, MajorLanGod wrote:
>>> Since when did a .jpg file become a system file? I was deleting a
>>> music folder which contained some .jpgs of the album cover, etc., and
>>> Windows kept asking me if I wanted to delete this system file.
>>>
>>> As far as I know, a file with a .jpg extension has never been
>>> essential in keeping Windows running, so why are they treated like
>>> system files?
>>
>> Was this jpg the photo associated with music files in the same
>> directory? Was it's name folder?
>
>Yes it is. I have many albums loaded to my hard drive. Usually each album
>has several .jpg files showing the various covers, etc. And you guys are
>right. All of the .jpg files have the H&S attributes set. God knows why,
>but at least I now know what is going on. Now to figure out the best way
>to go through 700+ folders and turn the System attribute off.

There are lots of options available to you, but I'd probably use Bulk
Rename Pro because the whole operation, across 700+ folders, would take
only seconds.

https://www.bulkrenameutility.co.uk/

MajorLanGod wrote:

> All of the .jpg files have the H&S attributes set. God knows why, but
> at least I now know what is going on. Now to figure out the best way
> to go through 700+ folders and turn the System attribute off.

In an elevated command shell, run:

attrib /?

That shows you the arguments you can pass to the attrib program, like
the /s arg which is described as:

Processes matching files in the current folder and all subfolders.

My guess you would open an elevated command shell to make sure you can
change file attributes in the folders, and run:

<d:>
cd <path>
attrib -h -s * /s

<d:> is whatever is the drive letter to the parent folder. <path> is
the parent folder under which you want to change file attributes. The
attrib command would remove the hidden (-h) and system (-s) file
attributes on all files, and recurse the subfolders to do the same.

On 1/29/2022 1:20 AM, VanguardLH wrote:
> MajorLanGod wrote:
>
>> All of the .jpg files have the H&S attributes set. God knows why, but
>> at least I now know what is going on. Now to figure out the best way
>> to go through 700+ folders and turn the System attribute off.
>
> In an elevated command shell, run:
>
> attrib /?
>
> That shows you the arguments you can pass to the attrib program, like
> the /s arg which is described as:
>
> Processes matching files in the current folder and all subfolders.
>
> My guess you would open an elevated command shell to make sure you can
> change file attributes in the folders, and run:
>
> <d:>
> cd <path>
> attrib -h -s * /s
>
> <d:> is whatever is the drive letter to the parent folder. <path> is
> the parent folder under which you want to change file attributes. The
> attrib command would remove the hidden (-h) and system (-s) file
> attributes on all files, and recurse the subfolders to do the same.
>
or a batch using ForFiles and *.jpg attrib -s

MajorLanGod <lonelydad58@gmail.com> wrote:
[...]

> Yes it is. I have many albums loaded to my hard drive. Usually each album
> has several .jpg files showing the various covers, etc. And you guys are
> right. All of the .jpg files have the H&S attributes set. God knows why,

FWIW, I checked a few of my albums and their Folder.jpg files indeed
also have the H&S attributes set.

The file Details do not mention which program was used to rip the CDs,
but in my case it's very likely Windows Media Player or/and MusicBee [1].

> but at least I now know what is going on. Now to figure out the best way
> to go through 700+ folders and turn the System attribute off.

Doesn't File Explorer allow you to tick a box 'Do this for all files'
(or whatever it's called) when it hits the first Folder.jpg file during
the bulk deletion process?

[1] Theoretically it could be another program, but then I'd have to kill
you (plural) after telling you, because it's iTunes.

On 2022-01-26 07:01, Paul wrote:
> Summary: A JPG file is not "treated" to begin with.
>          It does not need any attributes, to get its job done.
>          But you can add attributes, to change the OS behavior a bit.
>          I would class this as a "bad sign" (tm). Should not happen.
>          Just don't double click the thing, until you have thorough
>          vetted the file. At least do Properties on it, for a
>          quick look. Check the name, look for extension trick.

What about that photo being used for desktop background or something? It
could be marked "system" to block accidentally deleting it.

--
Cheers, Carlos.

On 1/29/2022 11:28 AM, Zaidy036 wrote:
> On 1/29/2022 1:20 AM, VanguardLH wrote:
>> MajorLanGod wrote:
>>
>>> All of the .jpg files have the H&S attributes set. God knows why, but
>>> at least I now know what is going on. Now to figure out the best way
>>> to go through 700+ folders and turn the System attribute off.
>>
>> In an elevated command shell, run:
>>
>>    attrib /?
>> That shows you the arguments you can pass to the attrib program, like
>> the /s arg which is described as:
>>
>>    Processes matching files in the current folder and all subfolders.
>> My guess you would open an elevated command shell to make sure you can
>> change file attributes in the folders, and run:
>>
>> <d:>
>> cd <path>
>> attrib -h -s * /s
>>
>> <d:> is whatever is the drive letter to the parent folder.  <path> is
>> the parent folder under which you want to change file attributes.  The
>> attrib command would remove the hidden (-h) and system (-s) file
>> attributes on all files, and recurse the subfolders to do the same.
>>
> or a batch using ForFiles and *.jpg attrib -s
You do not need a third party program or worry about permission to do
the job you want. It is easily done using the Batch file command in a
text file. you then rename the text file with the *.bat extension

Go to the folder where you wish to work on the files using file
Explorer. In the folder, create a text document (RIGHT CLICK in a
blank area of the folder, NEW, TEXT DOCUMENT ) Type the batch
commands, ( ie attrib -h -s * /s) into the text document. Save the
text document. Then change the name from NewTextDocument.txt to
NewTextDocumen.bat. This creates an executeable that when left clicked
will execute the command in the file.
If you want a copy of the the changes to the files, modify the command to
attrib -h -s * /s > yourfile.txt.
This will create a file yourfile.txt with a list of all the files whose
attributes were changed.

One of the commands I use a lot is dir *.txt /s >myfile.txt.
Recent use of this command was in conjunction with my project to scan
7K+ slides. I want a text file in the folder telling about the pictures
in the folder.
"dir *.txt /s >myfile.txt" puts a list of the files with the txt
extension in the folder and sub folders into the file myfile.txt.
I then compare it to a similar list using dir /s >folderfile.txt.
If you do as I said you can usually execute the batch command regardless
of the security your company has placed on their system.

On 1/29/2022 4:17 PM, knuttle wrote:
> On 1/29/2022 11:28 AM, Zaidy036 wrote:
>> On 1/29/2022 1:20 AM, VanguardLH wrote:
>>> MajorLanGod wrote:
>>>
>>>> All of the .jpg files have the H&S attributes set. God knows why, but
>>>> at least I now know what is going on. Now to figure out the best way
>>>> to go through 700+ folders and turn the System attribute off.
>>>
>>> In an elevated command shell, run:
>>>
>>>    attrib /?
>>> That shows you the arguments you can pass to the attrib program, like
>>> the /s arg which is described as:
>>>
>>>    Processes matching files in the current folder and all subfolders.
>>> My guess you would open an elevated command shell to make sure you can
>>> change file attributes in the folders, and run:
>>>
>>> <d:>
>>> cd <path>
>>> attrib -h -s * /s
>>>
>>> <d:> is whatever is the drive letter to the parent folder.  <path> is
>>> the parent folder under which you want to change file attributes.  The
>>> attrib command would remove the hidden (-h) and system (-s) file
>>> attributes on all files, and recurse the subfolders to do the same.
>>>
>> or a batch using ForFiles and *.jpg attrib -s
>
> You do not need a third party program or worry about permission to do
> the job you want. It is easily done using the Batch file command in a
> text file. you then rename the text file with the *.bat extension
>
>
> Go to the folder where you wish to work on the files using file
> Explorer.   In the folder, create a text document (RIGHT CLICK in a
> blank area of the folder, NEW, TEXT DOCUMENT )   Type the batch
> commands, ( ie  attrib -h -s * /s) into the text document.   Save the
> text document.  Then change the name from NewTextDocument.txt to
> NewTextDocumen.bat.  This creates an executeable that when left clicked
> will execute the command in the file.
>
> If you want a copy of the the changes to the files, modify the command to
>  attrib -h -s * /s > yourfile.txt.
>
> This will create a file yourfile.txt with a list of all the files whose
> attributes were changed.
>
>
> One of the commands I use a lot is dir *.txt /s >myfile.txt.
>
> Recent use of this command was in conjunction with my project to scan
> 7K+ slides.  I want a text file in the folder telling about the pictures
> in the folder.
> "dir *.txt /s >myfile.txt" puts a list of the files with the txt
> extension in the folder and sub folders into the file myfile.txt.
>
> I then compare it to a similar list using dir  /s >folderfile.txt.
>
> If you do as I said you can usually execute the batch command regardless
> of the security your company has placed on their system.

The only problem would be if there are files in the folder or any
sub-folder that should have the attrib h or s. I suggest protecting
against that by using:
ForFiles /S /M *.jpg /C "ATTRIB -s -h"

On 1/29/2022 5:37 PM, Zaidy036 wrote:
> On 1/29/2022 4:17 PM, knuttle wrote:
>> On 1/29/2022 11:28 AM, Zaidy036 wrote:
>>> On 1/29/2022 1:20 AM, VanguardLH wrote:
>>>> MajorLanGod wrote:
>>>>
>>>>> All of the .jpg files have the H&S attributes set. God knows why, but
>>>>> at least I now know what is going on. Now to figure out the best way
>>>>> to go through 700+ folders and turn the System attribute off.
>>>>
>>>> In an elevated command shell, run:
>>>>
>>>>    attrib /?
>>>> That shows you the arguments you can pass to the attrib program, like
>>>> the /s arg which is described as:
>>>>
>>>>    Processes matching files in the current folder and all subfolders.
>>>> My guess you would open an elevated command shell to make sure you can
>>>> change file attributes in the folders, and run:
>>>>
>>>> <d:>
>>>> cd <path>
>>>> attrib -h -s * /s
>>>>
>>>> <d:> is whatever is the drive letter to the parent folder.  <path> is
>>>> the parent folder under which you want to change file attributes.  The
>>>> attrib command would remove the hidden (-h) and system (-s) file
>>>> attributes on all files, and recurse the subfolders to do the same.
>>>>
>>> or a batch using ForFiles and *.jpg attrib -s
>>
>> You do not need a third party program or worry about permission to do
>> the job you want. It is easily done using the Batch file command in a
>> text file. you then rename the text file with the *.bat extension
>>
>>
>> Go to the folder where you wish to work on the files using file
>> Explorer.   In the folder, create a text document (RIGHT CLICK in a
>> blank area of the folder, NEW, TEXT DOCUMENT )   Type the batch
>> commands, ( ie  attrib -h -s * /s) into the text document.   Save the
>> text document.  Then change the name from NewTextDocument.txt to
>> NewTextDocumen.bat.  This creates an executeable that when left
>> clicked will execute the command in the file.
>>
>> If you want a copy of the the changes to the files, modify the command to
>>   attrib -h -s * /s > yourfile.txt.
>>
>> This will create a file yourfile.txt with a list of all the files
>> whose attributes were changed.
>>
>>
>> One of the commands I use a lot is dir *.txt /s >myfile.txt.
>>
>> Recent use of this command was in conjunction with my project to scan
>> 7K+ slides.  I want a text file in the folder telling about the
>> pictures in the folder.
>> "dir *.txt /s >myfile.txt" puts a list of the files with the txt
>> extension in the folder and sub folders into the file myfile.txt.
>>
>> I then compare it to a similar list using dir  /s >folderfile.txt.
>>
>> If you do as I said you can usually execute the batch command
>> regardless of the security your company has placed on their system.
>
> The only problem would be if there are files in the folder or any
> sub-folder that should have the attrib h or s. I suggest protecting
> against that by using:
>  ForFiles /S /M *.jpg /C "ATTRIB -s -h"
Here is a list of all of the batch commands that are available in WIndows 10
These could all be placed in the bat file as I discribed above and run
as an executable.

https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/attrib
attrib [{+|-}r] [{+|-}a] [{+|-}s] [{+|-}h] [{+|-}i]
[<drive>:][<path>][<filename>] [/s [/d] [/l]]
{+|-}r Sets (+) or clears (-) the Read-only file attribute.
{+\|-}a Sets (+) or clears (-) the Archive file attribute. This
attribute set marks files that have changed since the last time they
were backed up. Note that the xcopy command uses archive attributes.
{+\|-}s Sets (+) or clears (-) the System file attribute. If a file
uses this attribute set, you must clear the attribute before you can
change any other attributes for the file.
{+\|-}h Sets (+) or clears (-) the Hidden file attribute. If a file
uses this attribute set, you must clear the attribute before you can
change any other attributes for the file.
{+\|-}i Sets (+) or clears (-) the Not Content Indexed file attribute.
[<drive>:][<path>][<filename>] Specifies the location and name of the
directory, file, or group of files for which you want to display or
change attributes.
You can use the ? and * wildcard characters in the filename parameter to
display or change the attributes for a group of files.
/s Applies attrib and any command-line options to matching files in the
current directory and all of its subdirectories.
/d Applies attrib and any command-line options to directories.
/l Applies attrib and any command-line options to the Symbolic Link,
rather than the target of the Symbolic Link.
/? Displays help at the command prompt.

VanguardLH <V@nguard.LH> wrote in news:mctccjgnj2k5$.dlg@v.nguard.lh:

> MajorLanGod wrote:
>
>> All of the .jpg files have the H&S attributes set. God knows why, but
>> at least I now know what is going on. Now to figure out the best way
>> to go through 700+ folders and turn the System attribute off.
>
> In an elevated command shell, run:
>
> attrib /?
>
> That shows you the arguments you can pass to the attrib program, like
> the /s arg which is described as:
>
> Processes matching files in the current folder and all subfolders.
>
> My guess you would open an elevated command shell to make sure you can
> change file attributes in the folders, and run:
>
> <d:>
> cd <path>
> attrib -h -s * /s
>
> <d:> is whatever is the drive letter to the parent folder. <path> is
> the parent folder under which you want to change file attributes. The
> attrib command would remove the hidden (-h) and system (-s) file
> attributes on all files, and recurse the subfolders to do the same.
>

You know, I've been doing this since MS-DOS 2.0, and I totally forgot
about the attrib command. Couldn't be much simpler than that. Thanks for
reminding me.