F5F Stay Refreshed Software Operating Systems The question is unclear. Could you clarify what SET46A6 refers to?

The question is unclear. Could you clarify what SET46A6 refers to?

The question is unclear. Could you clarify what SET46A6 refers to?

X
xRogueData
Junior Member
4
10-07-2016, 03:32 PM
#1
I checked the task manager and noticed the process SET46A6.tmp is active. When you open details, it shows NahimicSvc32.exe. Is this something suspicious?
X
xRogueData
10-07-2016, 03:32 PM #1

I checked the task manager and noticed the process SET46A6.tmp is active. When you open details, it shows NahimicSvc32.exe. Is this something suspicious?

K
KetzPlayer
Member
210
10-07-2016, 11:08 PM
#2
What makes up your computer setup? For laptops, it's the manufacturer of the laptop itself. For prebuilt desktops, it's the company that assembled the desktop. If you built it yourself, tell us which motherboard maker you used. Many brands rely on Realtek hardware—those chips power Ethernet, WiFi, audio, and more. Nahimic is just one name Realtek uses for their software and drivers.

If you're concerned, consider using Malwarebytes or Bitdefender (free trial available). That’s what antimalware and antivirus tools are designed to do.
K
KetzPlayer
10-07-2016, 11:08 PM #2

What makes up your computer setup? For laptops, it's the manufacturer of the laptop itself. For prebuilt desktops, it's the company that assembled the desktop. If you built it yourself, tell us which motherboard maker you used. Many brands rely on Realtek hardware—those chips power Ethernet, WiFi, audio, and more. Nahimic is just one name Realtek uses for their software and drivers.

If you're concerned, consider using Malwarebytes or Bitdefender (free trial available). That’s what antimalware and antivirus tools are designed to do.

C
carp3
Senior Member
572
10-08-2016, 05:55 AM
#3
Thanks for the quick response. It seems the Nahimic drivers were the issue, matching the virus name in the discussion.
C
carp3
10-08-2016, 05:55 AM #3

Thanks for the quick response. It seems the Nahimic drivers were the issue, matching the virus name in the discussion.