You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
Has anyone else seen this issue?
I believe, I’ve found an associated underlying cause to it on an 2020 Intel MBP in my case at least. It turns out that it seems to occur when my WiFi AP Deauthenticates the MBP. In /Library/Logs/CrashReporter/CoreCapture/WiFi I see folders the name MCMWLAN Net Deauthentication with data time stamps the correlate exactly with the time my AP Deauths the MBP for some reason (as yet unknown).
The Service is fine after a reboot.
MacBook Pro
I hear you. Perhaps you don't have the default settings or perhaps your Bootcamp partition is not mounted. If your Bootcamp partition is not mounted then Spotlight will not search it, so the Spotlight searching would not be the problem causing UVFSService CPU usage.
However, just to be sure, the Bootcamp partition will not appear under Macintosh HD. Macintosh HD is a partition, itself. The Bootcamp partition would appear _next to_ Macintosh HD. See attached image.
I hear you. Perhaps you don't have the default settings or perhaps your Bootcamp partition is not mounted. If your Bootcamp partition is not mounted then Spotlight will not search it, so the Spotlight searching would not be the problem causing UVFSService CPU usage.
However, just to be sure, the Bootcamp partition will not appear under Macintosh HD. Macintosh HD is a partition, itself. The Bootcamp partition would appear _next to_ Macintosh HD. See attached image.
Okay, I found the solution and the problem was a simple one. The clue was an older post about the UVFSService being related the filesystem which was hinted at in the name plus the mds service running often at the same time. Also, I have several Macs, some Intel, some Apple Silicon. Only this Mac exhibited the issue.
In my case at least the solution was to exclude the Bootcamp partition from Spotlight which immediately solved the issue. After 24 hours, I can confirm the problem has not reappeared.
Prevent Spotlight from searching the Bootcamp partition by going to System Preferences -> Spotlight -> Privacy and click the "+" button. Scroll down to find the drive on the left named "Bootcamp" then click "Choose". This assumes the Bootcamp partition retains the default name for the partition and is mounted.
I have been dealing with this for ~2 months. My hard drive was being thrashed which affected the whole operating system being sluggish. This would occur after rebooting from Bootcamp to MacOS. My standard fix was to force quit UVFSService using Activity Monitor. This also caused Bootcamp to be unmounted and disappear from the desktop.
I had to reboot so the MacOS would remount my drives before I could go to System Preferences -> Spotlight -> Privacy and excluded the Bootcamp partition from Spotlight.
Thank you to whoever figured this out.
I also had trouble trying to find the Bootcamp partition, you need to click the tiny drop down arrow next to "Locations" then you will see bootcamp next to Macintosh HD and any other drives you might have.
Please remove this post as while a Crash does occur when the WiFi AP deauths the device. After a reboot and a bit of time the UVFSService does return to constant 25 - 35% CPU usage.
I have the same problem. Would you be able to tell me how to exclude my Bootcamp partition from Spotlight?
So I tried that, but I cannot find the bootcamp partition. I see my Macintosh HD, drilled down a little to look around, but nothing.
Mac UVFSService CPU Usage
