Macbook Air + Win 10 1903 (WDF_Violation)

Deleted member 77746 · 22 May 2019 at 07:05

Is anyone using Windows 10 on their Mac? Could you let me know your model please and did you install it via bootcamp?

The reason I am asking is I am searching for a file called MacHalDriver.sys from c:\windows\system32 but need a later version.

When installing 1903 on my Macbook Air 2011 13" model I get a WDF_Violation BSOD. One way to fix this is to replace this sys with a version from a later model.

I am booted into my mac now on 1903 with windows 10, however I have had to disable this driver until I find a later version.

Could you please upload your driver from above location please? Just this one file will be great but has to be from a Windows 10 install.

If anyone wants the .sys file here it is! I have tested and now all functions of my keyboard is now working and no more BSODS!

- ( MacHALDriver.sys )

Thanks

Deleted member 77746 · 22 May 2019 at 07:41

It's fine I got it using Brigadier !

https://www.intowindows.com/brigadier-download-boot-camp-drivers-without-boot-camp-assistant/

https://github.com/timsutton/brigadier/releases

Deleted member 77746 · 28 May 2019 at 22:26

You don't even have to do that, all you need to do is rename it. If it's renamed to .bak or something like that then that file doesn't load on startup anyway. No registry key editing is required.

Deleted member 77746 · 3 Jul 2019 at 15:49

Just a quick update, it looks like Apple has now acknowledged this issue and is fixing it permanently. Just funny how I resolved this issue in May.

https://appleinsider.com/articles/1...windows-10-update-over-boot-camp-driver-issue

Deleted member 77746 · 27 Jul 2019 at 13:10

You don't need to do anything with the registry at all. 4 easy steps.

1) Go to c:\windows\system32
2) Rename MacHALDriver.sys to MacHALDriver.bak
3) Copy over the file from the first post here to c:\windows\system32
4) Reboot.

Deleted member 77746 · 28 Jul 2019 at 07:50

A.Bss said:
thank you mrbell1984, However, even when i follow your steps, i still end up with the same issues.
I even tried renaming my old MacHALDriver back to see if that changed anything but it didn't. That's why i turned to registry to see if i could maybe do something there but i found that i don't even have a registry for MacHALDRiver and i think that is maybe why it makes no difference which file i use.

thoughts?

It's a MacBook air right? What model?

Deleted member 77746 · 28 Jul 2019 at 13:22

A.Bss said:
yes it is an A1369

Then what I said should have worked. With no problems.

Deleted member 77746 · 29 Jul 2019 at 10:59

Something must have been broken then in windows, at least it's sorted now.

Deleted member 77746 · 29 Jul 2019 at 12:08

A.Bss said:
indeed.

I also checked the registry and it's there now. I'm guessing what must have happened is - on my first attempt when i replaced the .sys file, Windows automatically removed it from registry to prevent it from booting. I think it may be a safety feature of some sort. I done that without going into Safe Mode which i want to point out because i think it's very important to be in Safe Mode for this whole thing to work properly.

Nope I never used safe mode and it worked fine.

Deleted member 77746 · 29 Jul 2019 at 16:34

A.Bss said:
It's just without Safe Mode, i got a BSOD with a WDF VIOLATION as soon as it made it to the desktop.

I did it without Safe Mode first before updating to 1903 but then after the update, Windows got rid of the registry and stopped loading MacHALDriver altogether.

Maybe they changed something since my version that was working. Possibly...

Deleted member 77746 · 16 Aug 2019 at 11:09

Reda said:
Hello There I am a MacBook pro user (13" late 2011) and I have been having a problem when I install the Bluetooth driver then I get a WDF_VIOLATION blue screen and while im here my windows 10 is also not supporting my speakers no aux Plz Help!!

I know nothing about the pro model. Only thing I can suggest is a fresh install with bootcamp drivers since it's a pro late 2011.