Boot camp unbootable, boots windows repair

Question

Level 1

8 points

Boot camp unbootable, boots windows repair

After not using my computer for a while (turned off) I booted it back up to windows through boot camp. After I left the computer overnight, taking into mind there was a scheduled update for windows. I came back to use it and windows seemed to not be working anymore. When windows is booted up it goes to windows repair. I ran CHKDSK using the CMD Prompt and majority of the partitions cannot be read so I canceled because of how long it was taking. When I went onto the OS X side, the windows is still readable, files can be accessed etc. However in the disk utility info option the boot camp partition says that it is unbootable (by saying no) the rest of the values also say no. What do I need to do to fix this issue? Without data being lost.

Thank you for your time and replies!

Extra info

Operating: Windows 7 Professional

I have no recent backups of windows

Using 2 external HDD disks

Mac mini 2018 or later

Posted on Apr 13, 2019 5:38 AM

Reply

Answer 1

Loner T

Level 9

59,520 points

Apr 13, 2019 11:44 AM in response to _Josh_h12

_Josh_h12 wrote:

So does this mean the version of Mac OS that I have installed may be causing the problem?

No.

Or are you requesting more information.

Yes.

If so, (that I need a older version) how will I go about that?

You do not need an older version. What is the current macOS version?

Reply

Answer 2

Loner T

Level 9

59,520 points

Apr 14, 2019 8:22 AM in response to _Josh_h12

_Josh_h12 wrote:

yes I can see my windows files in finder and I’m not sure wether my external hard drives are NTFS

I recommend you disconnect all external disks.

other than that no I’m not using any third party NTFS drivers.

If you can, I suggest you make a copy of all your non-OS files from the macOS side, to an external disk.

Reply

Answer 3

Loner T

Level 9

59,520 points

Apr 14, 2019 10:41 AM in response to _Josh_h12

Apple has a read-only NTFS driver, while Windows has a read-write driver. Under normal circumstances, they do not compete/race with each other. Third-Party drivers can cause conflicts.

In your specific case, it seems to be corruption within NTFS. Power outages or crashes can leave NTFS corrupt, which is typically checked when you boot Windows the next time. Partial Driver updates or Windows Updates can also cause this issue. I will normally only apply Security Updates manually.

Reply

Answer 4

_Josh_h12 Author

Level 1

8 points

Apr 13, 2019 10:58 AM in response to Loner T

It’s best I share what I’m seeing. Just to note on the boot camp first aid and partition aren’t a option.

I ran chkdsk on the c: drive

Reply

Answer 5

_Josh_h12 Author

Level 1

8 points

Apr 13, 2019 11:58 AM in response to Loner T

Thanks

Reply

Answer 6

_Josh_h12 Author

Level 1

8 points

Apr 14, 2019 2:57 AM in response to Loner T

I’m 2 hours in the chkdsk check and it’s still at 0 percent and presenting errors as shown.

Reply

Answer 7

_Josh_h12 Author

Level 1

8 points

Apr 14, 2019 7:16 AM in response to Loner T

How do I check that?

Reply

Answer 8

_Josh_h12 Author

Level 1

8 points

Apr 14, 2019 7:36 AM in response to Loner T

Says my my bootcamp partition is healthy

Reply

Answer 9

Loner T

Level 9

59,520 points

Apr 13, 2019 7:56 AM in response to _Josh_h12

Is your Windows installation on an external disk?

Reply

Answer 10

_Josh_h12 Author

Level 1

8 points

Apr 13, 2019 9:57 AM in response to Loner T

No, it’s internal on a Mac mini

Reply

Answer 11

Loner T

Level 9

59,520 points

Apr 13, 2019 10:40 AM in response to _Josh_h12

Can you post the output of

diskutil list

Chkdsk should be run only on C:. If Windows writes a signature to a non-NTFS partition, you will lose macOS.

Reply

Answer 12

Loner T

Level 9

59,520 points

Apr 13, 2019 11:35 AM in response to _Josh_h12

The Terminal version of

diskutil list

contains much more information.

First Aid is a macOS construct and does not work well on NTFS partitions. Older macOS versions can check FAT partitions.

Reply

Answer 13

_Josh_h12 Author

Level 1

8 points

Apr 13, 2019 11:41 AM in response to Loner T

So does this mean the version of Mac OS that I have installed may be causing the problem? Or are you requesting more information. If so, (that I need a older version) how will I go about that?

Reply