Boot Camp Crashes in Windows 10 1903

Riverside_Guy wrote:

SOOO, what I want to know is exactly what functions does Boot Camp Manager give me... i.e. what am I missing?

There are two key executables (this is from a Unix find in /Volumes/BOOTCAMP)

./Windows/System32/AppleControlPanel.exe
./Windows/System32/AppleOSSMgr.exe

Also, you can look in Windows Services for all Apple Services. For example, Apple Bonjour is supported when Apple BC drivers are installed.

iciconnect wrote:

My apologies I didn’t know Apple paid people to closely monitor the conversations regarding non supported BootCamp 6.0 systems.

Unless someone from ASC objects, conversations are not really censored.

I won’t post again since my love and passion is for the older capable hardware that has been deemed obsolete.

It is 'legacy', not obsolete. 😉

Im just happy Windows 10 1903 works on my aged and now vintage 2009 Cheese Grater Mac Pro.

You can also try the iMacPro drivers as a test.

@iciconnect Yes, I was circumspect at first, not knowing what stance ASC would take to discussing what really are very legitimate, maybe not officially sanctioned, ways to get our gear performing properly. Then I see of seemingly more importance to them, the word "d*a*m*n, that I used, get censored out (leaving everyone the impression I used something far stronger). Loner provided a link to an older discussion revolving around much the same issues that still exists here, so it looks like talking about non-officially sanctioned methods to correct what really are bad practices on Apple's part (i.e. their own update mechanism IN win10 did not replace the bad executable) are seen as legitimate discussion. See anyone from Apple in here trying to help out?

For MANY, MANY years I touted buying Macs BECAUSE it had something like BootCamp. The unfortunate truth is it's a hot mess. This is not in any way the Apple of old, the Apple of Raskin, Hirschfeld, Atkinson.

Just be thankful that their are some end users, like Loner, who make the effort to help out. At least, now that he kinda pointed in that direction to address my issue, I have more confidence it may work (I had actually researched it before he mentioned it).

It may not be related to 'bad' practices by Apple, but rigors of certifying software on 'older' hardware. W10 is supported on 2012 hardware, which is 6+ years old. 10+ year old hardware is much more difficult and time consuming. ROI on such platforms, no matter how much we, as consumers, may like them, is difficult to quantify, at best.

Well, the issue of ROI may be interesting... while I can only speak 100% for myself, I'm willing to bet there are a LOT of folks just like me... I find it annoying when they had the mechanism to fix my BC issue, they did not. More importantly, I firmly believe that absolutely NOBODY was clamoring for such a high end machine that MAY be many tens of thousands of dollars. They did NOT give us the machine so many of us have been talking about for the past half decade. Clearly, they see big financial gains in their services business. I KNOW what I want, and they do NOT make anything even close to what I want. I am NOT alone here, every pro I know feels the same way. My cMP is going to be the last hardware fro Cupertino (well, I exclude the tablet, it is very possible I may buy one if mine gets lost or heavily damaged). I will ALSO be 100% uninclined to subscribe to ANY of their services. AND I know I;m just one person and they simply don't care. Like I said, this ain't the Apple I grew up with.

Back on topic, I have achieved SUCCESS! There were some scary moments where stuff was happening too quickly for me to follow them (not to mention I had to figure out how to launch their terminal with the privileges I already had an administrator, most of the 2,000 techniques involved the "windows key!"). Past few weeks I have been in terminal so very slowly stuff started coming back to me.

So I see the "correct" version of the Control Panel. I re-enabled Task/Startup for "Boot Camp Manager." NO BSOD, in the hidden icon thing I found the CP. Instead of my startup volume name, it just said Mac... but DID list 2 other drives that CAN start up. Went with mac and shut down... then powered up. Hmmm, verbose mode? Then I'm back in macOS. Very curious why it did that? I have this sneaky feeling that maybe some of the stuff that does not seem to stick at first (i.e. prefs) may happen because they don't get written to disc with a restart, but may with a shut down. I guess I hit it right at least 50%+ with gut feelings <lol>.

1709 worked. Thanks a lot.

rajavsekar wrote:

1709 worked. Thanks a lot.

Excellent!

I have a 2009 Tower, and am happy to stay on W7, instead of W10. In my case, usage does not require newer Microsoft software. I have a PowerPC Mac, which is fully functional. 😉I also have a 2016 Mac, so a large time span is covered.

I understand your frustration with a 2010 MP not supporting a 2015 Windows OS, yet High Sierra (2017) supports your MP.

Regarding Paragon NTFS, look at the Reason 2 description.

Apple made a conscious choice not to regression test older hardware/drivers on newer OSes. This is directly related to revenue streams.

Also, remember there is a new cheese grater coming to an Apple Store near you this fall - Mac Pro - Apple. The primary reason being customer feedback. 😉

Since you have a working/functional system, which meets your needs you should be fine.

Regarding HS/Mojave and lack of W7/W8.1 support, I have stayed away from either (and on Sierra), to avoid the APFS-related issues, on Macs I control.

Corporate Macs are someone else's responsibility.

Over the last 5+ years, I have stopped buying new Macs, and wait an year or more to buy refurbished Macs which can be discounted up to 15%. I will buy the 2019 'Tower' in 2020, when it is about 6+ months old, and 'refurbished' gear starts showing up. I have no plans to buy a 6K monitor and a 1K stand, unless Mr. Cook sends me a fully-loaded system for free. I am not very fond of the cMP.

There is some built-in NTFS functionality in macOS. See /System/Library/Filesystems/ntfs.fs/Contents/ for available functions.

The NTFS Startup disk issues can also come about with Parallels, VMware, VirtualBox, NTFS-3g, MacFUSE or OSX-FUSE, etc.,.

BTW, I have the original MacBook Air, running Snow Leopard. It is still a fantastic little device, and Safari still works, but some newer features of websites cause issues. Many of us old-timers consider Snow Leopard the finest version of macOS.