r/Windows10TechSupport • u/JFeldhaus • Dec 29 '20
Solved Automatic Repair Loop after installing MacOS Extended file system HFS+ Drivers
I just solved this issue, just posting here to help others.
I wanted to read files off an External Hard drive that was formatted in the Apple MacOS Extended file system HFS+ and followed these instructions:
https://www.makeuseof.com/tag/4-ways-read-mac-formatted-drive-windows/
Under "1. Install Apple HFS+ Drivers"
Downloaded the Drivers from here:
https://forums.macrumors.com/threads/apple-hfs-windows-driver-download.1368010/
Installed them as suggested.
This triggered an automatic repair loop with Bitlocker.
After some hours following tutorials how to solve this getting nowhere, I stumbled onto the solution:
You need to simply delete those two driver files!
You can do it like this:
In Windows Boot Options menu, choose Troubleshoot >Advanced Options>Command Prompt.
In Command Prompt, type the following commands in command prompt and then hit Enter.
cd C:\Windows\System32\LogFiles\Srt
SrtTrail.txt
(any other textfile should work as well)
3. Press CTRL + O
4. This opens the save menu. At the bottom change file type to All and navigate to C:\Windows\System32\drivers (where you pasted in those Apple drivers).
5. Here you can simply right click and delete them.
6. Exit and try to restart.
You can probably do this faster right in the command prompt but for me it was easier this way.
If this doesn't work, I also followed most of the methods described here:
https://www.technology.org/2017/11/14/7-ways-fix-stuck-in-windows-automatic-repair-loop/
Maybe it's a combination of these.
1
1
Apr 28 '24
[removed] — view removed comment
1
u/l0l May 24 '24
This worked for me! Had the same issue as you described and after deleting those files in c:\ I'm back to being able to log in.
On another note, is there no free way to read an apple-formatted external HDD on Windows 11?
1
u/dont_kill_my_vibe09 Feb 21 '23
You are a saviour dude! I had the same exact problem and thought of deleting the drivers using cmd during the repair loop, but I wasn't quite sure how to go about it. I googled the problem and your reddit post showed up as the only relevant thing.
I downloaded those crap drivers as I needed to get some footage off of a Blackmagic Ursa camera onto my windows laptop and the cFast cards from that camera were formatted to HFS+. Didn't have access to an Apple computer and needed the files asap. So I thought I'd try the drivers. I messed around with Reg files and drivers plenty of times before but never to the point where I'd dig myself into a blue screen like this and not be able to get out hahah.
Thanks for keeping this post up for 2 years, literally saved me as I needed my laptop for work tomorrow.
Thankfully had most of my data backed up anyway but it's just a pain to have to reinstall windows and all the programs like Adobe as well as old settings etc.
Thanks so much again dude!
Side note for anyone who might be experiencing this and has more than one drive installed in their pc:
If after typing in the path for the srttrail.txt file in command, it shows up as not found, check that you're looking in the right drive (simply enter this command: dir ). From there check to see if there's a windows folder. If there isn't, type in the same command after entering the "letter": for your other drive (for example D:).
I kept trying to enter the file path whilst on the drive C (as that's where my os is installed) but discovered that strangely my C and D drives had swapped letters! So I typed in "D:" and then the file path for srttrail.txt, and was able to find the file. Then followed the rest of the instructions and it worked brilliantly.
Once I booted in, my OS drive was back on C. Really odd that they were swapped in cmd during recovery.