BootRunner 3.4 comeback to OSX Mojave after starting on Windows disk

aescalle · December 3, 2020, 2:52pm

Hello,

I get this issue: BootRunner 3.4 is always returning in Mac OSX after launching Windows HD.

I am running BootRunner 3.4 on a Mac Pro running OSX 10.14 on SSD,
and an HD with Windows 10.
(I actualy work on a Macpro Mid 2010 Mojave - Flashed 5.1 - 12 core - Graphic card Sapphire 580 - No boot screen - Using old Graphic card for access to it - 64Gb)

I did the “csrutil disable” command on the terminal through the recovery mode.
I’ve created a profle ans instal it
Automatic boot on the OSX SSD - disk0
And Bootcamp Windows as second - disk4

The Bootrunner screen at first was just freezing on “Restarting”,
And after changing my profile in checking All days of the week for the reboot,
BootRunner is now restarting Windows disk but going directly in my Mac OSX session.
I can’t reboot on my Windows 10 HD!

I get this result on the log file:

2020-12-03 16:10:49.535721+0100 localhost Boot Runner[290]: DiskDevice: Attached Disks: (
DiskDevice “File Path: /\n MBR: <>\n File System Size:0\n Drive Path: /dev/disk1\n Device: /dev/disk1s1\n Disk Name: Macintosh SSD\n Readble Size:479,76 GB\n File System Type: apfs\n Free Space: 197112160256\n Total Size: 479760007168\n”,
DiskDevice “File Path: /private/var/vm\n MBR: <>\n File System Size:0\n Drive Path: /dev/disk1\n Device: /dev/disk1s4\n Disk Name: vm\n Readble Size:479,76 GB\n File System Type: apfs\n Free Space: 197112160256\n Total Size: 479760007168\n”,
DiskDevice “File Path: /Volumes/BOOTCAMP\n MBR: <>\n File System Size:0\n Drive Path: /dev/disk2\n Device: /dev/disk2s2\n Disk Name: BOOTCAMP\n Readble Size:999,08 GB\n File System Type: ntfs\n Free Space: 381069697024\n Total Size: 999081799680\n”
DiskDevice)
2020-12-03 16:10:49.536215+0100 localhost Boot Runner[290]: DiskDevice: -----------/-----------
2020-12-03 16:10:49.536226+0100 localhost Boot Runner[290]: DiskDevice: iterating over disks and adding custom names
2020-12-03 16:10:49.536250+0100 localhost Boot Runner[290]: DiskDevice: Checking if bootable
2020-12-03 16:10:49.536340+0100 localhost Boot Runner[290]: DiskDevice: isBootable: File Path: /
DiskDevice MBR: <>
DiskDevice File System Size:0
DiskDevice Drive Path: /dev/disk1
DiskDevice Device: /dev/disk1s1
DiskDevice Disk Name: Macintosh SSD
DiskDevice Readble Size:479,76 GB
DiskDevice File System Type: apfs
DiskDevice Free Space: 197112160256
DiskDevice Total Size: 479760007168
DiskDevice
2020-12-03 16:10:49.536351+0100 localhost Boot Runner[290]: DiskDevice: isBootable: YES
2020-12-03 16:10:49.536361+0100 localhost Boot Runner[290]: DiskDevice: /: volume is bootable
2020-12-03 16:10:49.536371+0100 localhost Boot Runner[290]: DiskDevice: /:We have HFS
2020-12-03 16:10:49.536656+0100 localhost Boot Runner[290]: DiskDevice: morphing list to include additional pieces
2020-12-03 16:10:49.537095+0100 localhost Boot Runner[290]: DiskDevice: -----------/private/var/vm-----------
2020-12-03 16:10:49.537106+0100 localhost Boot Runner[290]: DiskDevice: iterating over disks and adding custom names
2020-12-03 16:10:49.537123+0100 localhost Boot Runner[290]: DiskDevice: Checking if bootable
2020-12-03 16:10:49.537160+0100 localhost Boot Runner[290]: DiskDevice: isBootable: NO
2020-12-03 16:10:49.537171+0100 localhost Boot Runner[290]: DiskDevice: -----------/Volumes/BOOTCAMP-----------
2020-12-03 16:10:49.537180+0100 localhost Boot Runner[290]: DiskDevice: iterating over disks and adding custom names
2020-12-03 16:10:49.537196+0100 localhost Boot Runner[290]: DiskDevice: Checking if bootable
2020-12-03 16:10:49.537236+0100 localhost Boot Runner[290]: DiskDevice: isBootable: /Volumes/BOOTCAMP/Windows/System32
2020-12-03 16:10:49.537246+0100 localhost Boot Runner[290]: DiskDevice: isBootable: YES
2020-12-03 16:10:49.537255+0100 localhost Boot Runner[290]: DiskDevice: /Volumes/BOOTCAMP: volume is bootable
2020-12-03 16:10:49.537266+0100 localhost Boot Runner[290]: DiskDevice: /Volumes/BOOTCAMP: We have NTFS or msdos
2020-12-03 16:10:49.537477+0100 localhost Boot Runner[290]: DiskDevice: morphing list to include additional pieces
2020-12-03 16:10:49.537921+0100 localhost Boot Runner[290]: DiskDevice: check prefs
2020-12-03 16:10:49.537941+0100 localhost Boot Runner[290]: DiskDevice: Automatically selected volume option in effect…Checking for volume name or device to select…
2020-12-03 16:10:49.538046+0100 localhost Boot Runner[290]: DiskDevice: No volume with name:disk1. Not selecting.
2020-12-03 16:10:49.538192+0100 localhost Boot Runner[290]: DiskDevice: (
DiskDevice “File Path: /\n MBR: <>\n File System Size:0\n Drive Path: /dev/disk1\n Device: /dev/disk1s1\n Disk Name: Macintosh SSD\n Usage: macOS\n\nmacOS is a series of graphical operating systems developed and marketed by Apple Inc. since 2001.\n\nSource: Wikipedia\n\n Readble Size:479,76 GB\n File System Type: apfs\n Free Space: 197108088832\n Total Size: 479760007168\n”,
DiskDevice “File Path: /Volumes/BOOTCAMP\n MBR: <>\n File System Size:0\n Drive Path: /dev/disk2\n Device: /dev/disk2s2\n Disk Name: BOOTCAMP\n Usage: Windows\n\nMicrosoft Windows is a group of several graphical operating system families, all of which are developed, marketed, and sold by Microsoft.\n\nSource: Wikipedia\n\n Readble Size:999,08 GB\n File System Type: ntfs\n Free Space: 381069697024\n Total Size: 999081799680\n”
DiskDevice)
2020-12-03 16:10:49.538203+0100 localhost Boot Runner[290]: DiskDevice: There were 2 disks found
2020-12-03 16:10:50.076016+0100 localhost Boot Runner[290]: (LaunchServices) [com.apple.launchservices:default] LSExceptions shared instance invalidated for timeout.
2020-12-03 16:10:51.155593+0100 localhost Boot Runner[290]: (ViewBridge) +[NSXPCSharedListener endpointForReply:withListenerName:]: an error occurred while attempting to obtain endpoint for listener ‘ClientCallsAuxiliary’: Connection invalid
2020-12-03 16:10:51.157298+0100 localhost Boot Runner[290]: (CoreFoundation) [com.apple.CFPasteboard:entry] ResolveAllPromisedData called

Any idea to help me ?

Thank you in advance

tperfitt · December 3, 2020, 10:39pm

Can you try Boot Runner 3.2 and see if it resolves the issue?

I think there may be a regression.

tim

aescalle · December 4, 2020, 8:31am

Thank you Tim,
I will try today this and comeback to you.

aescalle · December 4, 2020, 10:33am

Hi Tim,

Well,
I just did a new install with the BootRunner 3.1 version,
but the problem is still the same. still comeback to the OSX mojave

I tried also to put BOOTCAMP hard drive on automatic restart but still comeback to the OSX mojave session

Same result in adding a third HD with SIERRA
Same result in changing profile from Undefined to EFI
Same result in changing profile from Undefined to Volume EFI

aescalle · January 2, 2021, 5:27pm

Hi Tim @ tperfitt,
I am stuck and waiting for support.

I get the feeling a lot of people have problems with BootRunner…

How I can get to make it working ?

In the waiting of reading you or someone else

Thank you in advance
Best

Stu2366 · January 26, 2021, 4:27pm

Hello aescalle. Did you have any luck resolving this issue? I have a near identical setup to yours. Thx.

aescalle · January 26, 2021, 4:54pm

Hi @Stu2366,
No no nothing ;-(
And no more official support to.

As I can see it is the mess for a lot of users.
I think it is a waste of money!

tperfitt · January 27, 2021, 4:38pm

Please send me the log:

Logging Options

Boot Runner logs messages via the Apple System Logger. To view the logs, open Terminal and enter in the following command:

log show --style syslog --predicate ‘process contains[cd] “Boot Runner”’ --info --last 2d

You can adjust the “2d” for a longer or shorter time period. You can specify a number and then m (minutes) h (hours) or d (days). For example: “–last 2m” or “–last 3h”.

To send the output to a file, redirect the output:

log show --style syslog --predicate ‘process contains[cd] “Boot Runner”’ --info --last 2d > ~/Desktop/bootrunner.log

This will save the last 2 days of Boot Runner output to a file on the current user’s desktop called “bootrunner.log”.

tim

Stu2366 · January 27, 2021, 9:12pm

Hello Aescalle. I fixed my issue on my end earlier today by doing a complete uninstall of V3.4 using the uninstaller embedded in the DMG file for Boot Runner. Like you, I had V3.1 installed (no joy), followed then by 3.4 and was getting the same results as you. I tried several of the options in Force Boot type in the Boot Runner web-based Profile. Again no joy.

Solution: I then installed V3.2 using the link that Tim provided. I can boot from Mojave, or from either of the Win7 Ultimate SSDs that I was testing. Since we have pretty much identical upgraded Mac Pros (the only difference being you are using Win 10 I believe), maybe give another “kick at the can” and do what I did?

One last thing…Like you (I think that this was in a separate post by you?), I was getting weird results when using Terminal in the Recovery system. After some trial and error, what I ended up doing was the following.

Command-R into Recovery, then Terminal then used “csrutil disable”.
Rebooted into Mojave. Opened Terminal to check status “csrutil status” - confirmed SIP was disabled.
Back to Recovery (Command-R), Opened Terminal and typed: “csrutil enable --without nvram”.
Restarted and back into Mohave.
Terminal: “csrutil status” and got the following info:
System Integrity Protection status: enabled (Custom Configuration).

Configuration:
Apple Internal: disabled
Kext Signing: enabled
Filesystem Protections: enabled
Debugging Restrictions: enabled
DTrace Restrictions: enabled
NVRAM Protections: disabled
BaseSystem Verification: enabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

I hope this helps. Stu.

aescalle · January 28, 2021, 7:42am

hello @Stu2366 & @tperfitt

Thank you for your help I will go back to my computers in the next hours and tell you what happen… !