Just had an occasion to email an a .EXE file , previously I always just renamed it with .txt extension, and no problem.
But what ever I did Win10 insisted on sticking a .EXE extension on the end.
I had to resort to my old WIN-XP to do it.
Something to do with Administrator rights maybe?

 

Just had an occasion to email an a .EXE file , previously I always just renamed it with .txt extension, and no problem.
But what ever I did Win10 insisted on sticking a .EXE extension on the end.
I had to resort to my old WIN-XP to do it.
Something to do with Administrator rights maybe?

When you rename a file in Win10, you can’t change the extension… Unless you change the view to show file extensions (they’re hidden/ protected by default).

 

I can see all file extensions?

 

I can see all file extensions?

Hmmm… go to the File Explorer menu and select view.

Make sure the Hide extensions… is unchecked. I’ve accidentally renamed a file whatever.exe.exe while trying to rename a file extension. It happens.

 

I get a different menu in File Explorer?
But I managed to send it in the end, but now it kicks it back for unsuitable content, it is a motor tuning program. !?

 

I get a different menu in File Explorer?
But I managed to send it in the end, but now it kicks it back for unsuitable content, it is a motor tuning program. !?

I’m stumped.
This issue has happened to me before and this is how I resolved it. My Windows machine needs to be recharged… batteries dead so I can’t find what you may be seeing. Are you Win10 or Win11?

 

WIn10
I think the last error was with the yahoo email

 

WIn10
I think the last error was with the yahoo email

Sounds about right. Email providers have filters on attachments to make the spread of viruses more difficult.

 

I get a different menu in File Explorer?
But I managed to send it in the end, but now it kicks it back for unsuitable content, it is a motor tuning program. !?

This is probably not an OS issue, but rather something in the e-mail chain at one end or the other.

Many e-mail clients and service providers will block certain file types, with .exe files being at the top of the list. This is because of all the people out there that will click on a file they get from some random, unknown source without a care in the world -- and then will be mad when bad things happen and blame their service provider.

This can get out of hand, especially if the military gets involved. We had Python script we needed to send to someone and the e-mail system stripped it out of the e-mail as being dangerous content. So we changed the extension to .txt and told them in the e-mail to change it back. Didn't work, it recognized it as a Python script and stripped it out. So we zipped it up and sent the zip file. Didn't work -- it went into the zip archive, removed the file from the archive, and delivered an empty archive. So we renamed the file before zipping it up. Still didn't work. So we renamed the file, zipped it up, and then renamed the zip file. Didn't work. The system recognized the file as being a binary file (despite the .txt extension), recognized it as being a zip archive (based on the magic number in the file), unzipped the file and recognized the resulting text file as being a Python script, so it stripped it out. We finally had to encrypt the file and send it that way. When we asked the Comm Squadron why they were doing this, we were told it was so that recipients didn't "accidentally" run a malicious Python script. So let's think about the threat here -- I get an email from some unknown source that has a .txt file attached. I'm going to accidentally rename it to a zip file, then I'm going to accidentally unzip the attached zip file, accidentally change the extension from .txt to .py, accidentally install a Python interpreter, and then accidentally go out to the command line and execute the script.

 

Just .zip it.

 

The receiver sent me a couple of other email add, one of them worked with the *.txt file ext.

 

Just .zip it.

May work. Worth the attempt. Just hope that it's not passing through a system at some point that is overly paranoid. See my earlier post.

Another way is to uuencode it. I don't know how that would have worked in the situation we found ourselves in. You would think it would work -- but then we thought that zipping it would work.

 

I use Magic Wormhole for secure client to client transfers:

https://github.com/magic-wormhole/magic-wormhole

 

@MaxHeadRoom Hope you can handle the Spanish part of it.

BTW, no "clock" but "click"