Page 3 of 3 FirstFirst 123
Results 33 to 34 of 34

Thread: Microsoft working on fix for nasty NTFS corruption bug

  1. #33
    Banhammer in peace PeterB kalniel's Avatar
    Join Date
    Aug 2005
    Posts
    30,198
    Thanks
    1,689
    Thanked
    3,130 times in 2,531 posts
    • kalniel's system
      • Motherboard:
      • Gigabyte Z390 Aorus Ultra
      • CPU:
      • Intel i9 9900k
      • Memory:
      • 32GB DDR4 3200 CL16
      • Storage:
      • 1TB Samsung 970Evo+ NVMe
      • Graphics card(s):
      • nVidia GTX 1060 6GB
      • PSU:
      • Seasonic 600W
      • Case:
      • Cooler Master HAF 912
      • Operating System:
      • Win 10 Pro x64
      • Monitor(s):
      • Dell U2311H
      • Internet:
      • rubbish

    Re: Microsoft working on fix for nasty NTFS corruption bug

    Quote Originally Posted by Corky34 View Post
    Unless I've made a mistake "file:///" followed by the command mentioned in the article would, it's not the running of a file that causes the problem but simply trying to access it that causes it.

    I was trying it last week so i maybe misremembering but IIRC i was able to trigger a chkdsk by using "file:///" followed by the command in the article.
    Can you shorten those with a URL shortener? If so, then yes, possibly vulnerable to a shortener link

  2. #34
    Senior Member
    Join Date
    Dec 2013
    Posts
    3,246
    Thanks
    460
    Thanked
    416 times in 288 posts

    Re: Microsoft working on fix for nasty NTFS corruption bug

    That IDK, I've never used a URL shortener .

Page 3 of 3 FirstFirst 123

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •