Recommended Posts

This is maybe a bug, maybe not, but I think that this behavior should not happen at all, and in some ways gives you another perspective of how clipboard works.

Explanation

yesterday i was woking with some servers and copy a command to paste in a brand new txt file.

the command was \\192.168.1.1\c$

i selected the command and pressed ctrl-C

i right click desktop and created a new text file, but by error i pressed ctrl-V in the name of the txt file

Windows pasted 192.168.1.1c$ and told me that some characters will not do in a filename.

i pressed esc to get the original filename

opened the file name and pasted the clipboard content.

Now, what i pasted was 192.168.1.1c, so MY clipboard content was modified by windows.

I mean instead of modyfing the file name to remove the characters, windows modified my clipboard.

Link to comment
https://www.neowin.net/forum/topic/769870-discovered-bug-in-7-clipboard/
Share on other sites

Well, if anyone can report it, do it, i don't want any credit, only a more stable and coherent OS.

I will be using it for years to come.

BTW i found the "bug" in a 2003 remote terminal i was working on, so i opened my 7VM and tried it there. still alive as janek said.

That makes me think about how really clipboard works.

Also happens in XP. (My main OS at work(and as mike said)) and 2000. Maybe is one of a bunch of legacy windows bugs. who knows...

In another topic...

Also is nice (very nice and feels good) to find many other users like me, that have been around for years and years, and only make posts in forums to talk of meaningful things :p

Best regards

This is not the clipboard changing. It is the destination server taking out the illeagal characters for a file name. If you paste it into the new text file on the destination server it will be what you copied. If you paste it into a text file on the source machine it will be what you copied. Been there since vista at least.

Dave.

This is not the clipboard changing. It is the destination server taking out the illeagal characters for a file name. If you paste it into the new text file on the destination server it will be what you copied. If you paste it into a text file on the source machine it will be what you copied. Been there since vista at least.

Dave.

It's definitely changing the clipboard data. Pasting "\\192.168.1.1\c$" into a filename removes the invalid characters. Opening notepad and pasting immediately after resulted in the modified data being pasted into the text file: "192.168.1.1c$"

This has always been a bug, it's actually intentional.

Remember the /con/con bug of Win98? Microsoft fixed that, and in turn got rid of backslashes in actual filenames/folders to stop this bug.

You can actually create a folder called "\\192.168.1.1\c$" but my guess is that you have to create it within another OS.

I haven't tried that myself, but it may not be possible because of changes to the FAT32 and NTFS filesystems.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I've been on Deezer for over a decade, but glad that Tidal joined them in fighting AI slop. Can't stand such takes as Spotify's: "Spotify's CEO recently pushed back against listeners who call AI music "slop," urging people to stop using the term and instead embrace the creative potential of AI music."
    • “Could” … in the IS the healthcare is run by insurance companies that make indecent profits denying basic treatments to people that are paying money for nothing. Besides, where are all the Trump epigones who were stating that the tariffs were going to paid by foreign companies and not the US citizens? …
    • Microsoft Teams gets smarter at spotting sneaky meeting bots by Usama Jawad Microsoft Teams is set to receive a couple of new features soon, including a dedicated Recap app and a rather controversial location tracking functionality. The Redmond tech giant has also explained how it has made online communication and collaboration a lot more performant this year. Now, the company has detailed more secure bot admission mechanisms, as first reported by us in March 2026, and now available in Teams. As the use of AI has expanded across enterprise environments, Microsoft has begun allowing users to integrate bots into their meetings for various tasks, such as note-taking. While this has a tangible productivity benefit for users, Microsoft has highlighted how misconfiguration has allowed bots to join meetings that they shouldn't. This has created security and privacy risks, which Microsoft is now combating using a new Teams admin policy that allows organizers to control how external bots access meetings. Admins can leverage a policy called Manage external bots and their access to meetings. The default configuration is "When detected, require approval before joining", which places detected bots in a lobby before they are explicitly admitted into the meeting. The other option disables the experience. Microsoft has also requested admins to only allow organizers and co-organizers to manage access to a meeting, so that other people don't randomly allow bots into meetings. Teams will now be able to leverage infrastructure signals to intelligently detect and distinguish between bots and humans. Microsoft will soon also trial a registration experience for independent software vendors (ISVs) to build a system that registers a bot with Microsoft, so it is marked as a "known" bot. Teams will also categorize bots as trusted and suspected threats so that organizers can quickly identify which bots they want to allow into a meeting. Additional safeguards to block accidental admission of a bot into a meeting include: No one-click Admit option for identified bots Confirmation prompts when admitting participants that include bots Warnings when organizers choose Admit all, and bots are included Microsoft has begun rolling out this experience, and it will be retiring the current CAPTCHA verification implementation. In the future, the company plans to roll out new capabilities like allow-lists, organization-wide policies, admin reports, audit logs, and more granular controls.
    • With the current hardware prices Microsoft should lift the restriction. Then if you have the correct TPM then allow you to use X feature, if you don't have the correct TPM then don't but still actually let you run windows. 11. With a disclaimer during install that X features would be unavailable.
    • It's good for recycling of course. But commence inflation of a second hand RAM bubble and price gouging on DDR 4 inventory in 3... 2... 1...
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      538
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!