Hiding NTFS Volume Names in the Finder

Actually, 2 questions relating to the same thing. Just did a win10 install on it's own drive (a process that took a LOT of time to get done right). The "System Reserved" NTFS volume shows in the Finder... can I hide it without having any effect on win10 working? How? Second, the main win10 volume is showing as "untitled" and can not be changed on the Mac side (again, NTFS volume). CAN I change that me in the win10 side, or if not, can I also hide it from seeing it in the Finder (if I can't change it's name in win10)?

Mac Pro, macOS 10.12

Posted on Jun 16, 2019 2:14 PM

Reply

Similar questions

37 replies

Jun 17, 2019 6:33 PM in response to Riverside_Guy

diskutil info /dev/disk0s2
   Device Identifier:        disk0s2
   Device Node:              /dev/disk0s2
   Whole:                    No
   Part of Whole:            disk0


   Volume Name:              Windows10
   Mounted:                  Yes
   Mount Point:              /Volumes/Windows10


   Partition Type:           Windows_NTFS
   File System Personality:  NTFS
   Type (Bundle):            ntfs
   Name (User Visible):      Windows NT File System (NTFS)


   OS Can Be Installed:      No
   Media Type:               Generic
   Protocol:                 SATA
   SMART Status:             Verified
   Volume UUID:              D9044EAC-2CC1-40C3-BB11-6D91F8EC7084


   Disk Size:                499.5 GB (499498614784 Bytes) (exactly 975583232 512-Byte-Units)
   Device Block Size:        512 Bytes


   Volume Total Space:       499.5 GB (499498610688 Bytes) (exactly 975583224 512-Byte-Units)
   Volume Used Space:        24.2 GB (24211685376 Bytes) (exactly 47288448 512-Byte-Units) (4.8%)
   Volume Available Space:   475.3 GB (475286925312 Bytes) (exactly 928294776 512-Byte-Units) (95.2%)
   Allocation Block Size:    4096 Bytes


   Read-Only Media:          No
   Read-Only Volume:         Yes


   Device Location:          Internal
   Removable Media:          Fixed


   Solid State:              Yes
   Device Location:          "Bay 1"

Jun 18, 2019 8:11 AM in response to Loner T

The only things I did in diskpart was run "clean," then "convert mbr" with the target SSD selected. Then it was back to the setup UI. I just used the "New" button there (there was an entry of "unallocated space" in the disk list for my target SSD)... that created 2 partitions, System Reserved and Primary, then went to installing onto Primary.


That target disc IS MBR, partitions NTFS, my limited understanding/guess is that it may be booting in some legacy mode and not in EFI mode... I'm a bit fuzzy on the why and wherefores, but no question it works the way I expect (still have yet to figure out a way to have the win10 side ACTUALLY tell me the correct time, everything I CAN set has been set, still it puts me 3 hours AHEAD of my local time... stupid dumb m$ shizz, yeah what I expect!).

Jun 18, 2019 8:56 AM in response to Riverside_Guy

Your 2010 MP supports Windows in legacy Mode. You can either use a MBR disk or a GPT disk with Hybrid MBR. convert mbr makes it the former. Since it is working, we should leave it alone, unless you really want to address the MSR issue.


I have seen similar issue with Time Zone settings between Windows and macOS. If macOS has the correct time zone and syncs with a good NTP server, check if the Windows side is setup similarly.



Jun 18, 2019 9:21 AM in response to Loner T

My original goal was to not see the HD icons for either of the 2 NTFS volumes... I have come across some terminal magic that can hide them or not even let them mount under macOS. Assumption is this has no bearing on win10 booting or doing what it does (or doesn't do!). Was curious from folks who know more than I which one was a better way of making them disappear from my desktop.


macOS has been correctly set up, never an issue. Took me a while to GET to the right places (there are several of them!) in win10, but no question is KNOWS my current location, it KNOWS what time zone, AND i tried auto time zone w/auto sync and with auto time zone off as well, but it still advances my local clock 3 hours (somewhere out in the Atlantic ocean). Last time, I set it to manual with the correct time showing. I NOW recall back when I was doing 7 then 10 I had the same issue. Don't remember the reasons (some bug in the OS), but I remember doing some command line input that actually fixed the issue. Spent a ton of time goggling the issue, everything kept telling me to do what I had already done!

Jun 19, 2019 2:14 PM in response to Loner T

Indeed that sure is a possible solution... need a bunch of time to figure out an AppleScript that worked, it's been way many days since I wrote ANY code, I'm only barely starting to remember some terminal, command line stuff it's been so long! I DID find out that chflags won't work because it considers those volumes read only!


Apparently the issue with the time is macOS stores it in GMT, win stores it as local (I guess THEN applies the differential). As it was always 4 hours ahead, tried to cheese it by setting local and time offset to Alaska. Said auto-time zone, but it appears it isn't honoring that either! Friend said he thought on of the BC bits and pieces fixed that, BUT as you may know from the other thread, I just got hosed seemingly because I did 1903 from the install!

Jun 20, 2019 11:51 AM in response to Riverside_Guy

From https://support.apple.com/kb/DL1720?locale=en_US,


Post Date: Feb 11, 2014

File Size: 924.9 MB


System Requirements 

  • MacBook Air (11-inch & 13-inch, Mid 2011)
  • MacBook Air (11-inch & 13-inch, Mid 2012)
  • MacBook Pro (15-inch & 17-inch, Mid 2010) 
  • MacBook Pro (13-inch, & 15-inch, Early 2011)
  • MacBook Pro (17-inch, Early 2011)
  • MacBook Pro (13-inch,15-inch & 17-inch Late 2011) 
  • MacBook Pro (13-inch & 15-inch, Mid 2012) 
  • MacBook Pro (Retina, Mid 2012) 
  • MacBook Pro (Retina, 13-inch, Late 2012) 
  • MacBook Pro (Retina, 13-inch and 15-inch, Early 2013)
  • Mac Pro (Early 2009) 
  • Mac Pro (Mid 2010) 
  • Mac Pro (Mid 2012)
  • Mac mini (Mid 2011) 
  • Mac mini (Late 2012) 
  • iMac (27-inch, Mid 2010) 
  • iMac (21.5-inch & 27-inch, Mid 2011) 
  • iMac (21.5-inch & 27-inch, Late 2012)
  • iMac (21.5-inch) Early 2013
  • Windows 7, Windows 8, and Windows 8.1, 64 bit


There is no real BC 6.x release which supports W10. Some drivers did not change, so they will work, while others can cause issues.


However, the 2012 and 2013 MacPro have W10 drivers.


Jun 20, 2019 12:48 PM in response to Riverside_Guy

The following verbiage on the page ...


"

For more information on Boot Camp, click here: www.apple.com/support/bootcamp

Note: If you are using one of the Macs listed below, you should download Boot Camp Support Software 5.1.5640 instead.

  • MacBook Air (11-inch, Mid 2013)
  • MacBook Air (13-inch, Mid 2013)
  • MacBook Pro (Retina, 13-inch, Late 2013)
  • MacBook Pro (Retina, 15-inch, Late 2013)
  • Mac Pro (Late 2013)
  • iMac (21.5-inch, Late 2013)
  • iMac (27-inch, Late 2013)

"


confuses many readers.


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Hiding NTFS Volume Names in the Finder

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.