This blog has detail instructions to install USB WinToGo for Mac. But things won’t go that smooth on pre-2013 rMBP.
Firstly, diskpart from Windows cmd within Virtual Machine seems to have limitations, especially for Win8.1. Partitioning can work sometime but formatting will probably fail. Therefore, diskutil in Mac is the solution for disk handling. But another problem occurs. FAT32 partition is tried but found to cause errors during imagex transfer due to large file size restrictions. But disktuil doesn’t support NTFS. At last, NTFS partition is formatted with diskutil with the help of Paragon-NTFS 14 in El Capitan.
Secondly, “bcdboot /f ALL” will create EFI boot mode for usb drive, under which Win2Go can be successfully installed but instantly turns into black screen when installing bootcamp/nvidia drivers. It’s because that pre-2013 MBP is not fully compatible with UEFI crashing the graphics/audio drivers under EFI boot. The solution is to boot with CSM-BIOS mode. That means when booting MBP with alt, “Windows” is the only menu choice not “EFI”. Clearing the boot partition and “bcdboot /f BIOS” for BIOS boot mode section. However, the “none system disk” error shows when booting the “Windows” option.
Finally, this article sheds the light. “bootsect /nt60 x: /force /mbr” to force using the win8.1 bootmgr will boot your MBP into Win8.1, with all bootcamp drivers ready to be installed.
Enjoy the Win2Go, thanks for the almighty Google and a whole day of rebooting!
My windows 2003 vm in vmware fusion turns into a black screen after an OSX crash. The guest system seems bootable but starts with total blackness. Fortunately safe mode works. Event log shows it’s unable to load vmx_fb.dll, which is the graphics driver of vmware tools.
The paradox is that vmware tool is unable to install in safe mode, which will always fail even though MSI service can be enabled with this method. Then manually deleting vmx_fb.dll and vmx_mode.dll in system32 folder also not works.
It seems the only way is to roll back vm to 2-month-ago snapshot losing all the intermediate stuffs. But this thread is the rescue. Additional vmx_svga.sys in drivers directory should also be deleted. Then the guest 2003 system can be started with the default vga driver.
Now enter the vm, reinstall vmware tools, and make a new snapshot for such emergency case.
Just encountered a mysterious problem after upgraded to 10.11.4 that every time MBP reboots and logins, my trackpad settings like tap-to-click are lost. It’s mysterious because during the very beginning time after login it worked as normal, but a few minutes later trackpad settings were reset automatically. It also affected the Mac AirPlay to AppleTV which would not work except for the first few minutes after reboot.
Googling the airplay problem leads to login items. But removing all of my existing login items doesn’t fix the problem. (Of course, the trackpad plist is the first try which also doesn’t work.)
And the console log during possible resetting trackpad has messages like “kernel: Sandbox: CommCenter(3359) deny(1) file-read-metadata /Library/Developer” and “otherbsd: Could not submit LoginItem job com.XXX.XXXYYY: 119: Service is disabled”;
More googling doesn’t find much useful info. Similar keyboard reset problem exists but has no fix yet. When analyzing the details of the console logs, one interesting thing is that there’re two login window app started msg around that time, when the failed login items are all at the second login window session and possibly kill my trackpad settings and airplay.
Then why on earth exists another login window session? The culprit is _xcsbuildd. As 10.11.4 upgraded Mac Server, with XCode server service included, which will run as user _xcsbuildd at background. The upgraded service’s second login session breaks some login items which seems indeed killing airplay and resetting the trackpad settings.
Simply disable xcode service in Server.app will not remove _xcsbuildd related stuffs. Use this methods to totally get rid of it.
Finally reboot and enjoy the hassle-free trackpad and airplay again.
One of my relative’s iPad2 got stuck in the iTunes logo interface and unusable for a while. Just tried to get it restored when connected to iTunes via USB. However, it always auto rebooted after progress bar appeared under the Apple logo.
Tried DFU mode and restore still fails with “Unknown Error 9”. This thread googled suggests the unbelievable culprit: the latest iOS 9.2.1 is incompatible to restore iPad2.
Since older iOS version cannot be signed and updated by Apple now, latest iOS 9.3 beta 4 works fine to restore iPad2 successfully.
My iPhone6+ got stuck when uploading some photos automatically to iCloud Photo Library. It’s quite possible if the phone’s available free space is lower than 400MB when using optimizing size option, which might be required by the mysterious blackbox photo upload process. But after cleaning up disk space, it still paused at the “uploading xx photos” phase.
Tried everything googled: reboot phone / disable-enable iCloud Photo Library / delete videos / logoff iCloud account, nothing worked.
Finally, forget about the iCloud synchronization. Disable Photo Library, transmit these photos to Mac and manually upload photos to iCloud.com, then delete all existing photos from the phone. And at last re-enable the iCloud Photo Library to download all photos again to the iPhone.
Hope it will sync next time.
Just encounter a strange problem of key chain access. When prompting for access to credentials, the dialog can only be dismissed by Deny. In the console, “Ignoring user action since the dialog has received events from an untrusted source” was logged.
According to this post, 10.11.1 contains a security patch to prevent synthetic clicks on keychain dialogs. Try disabling all apps in the privacy settings of accessibility-mac-control, but not works.
Therefore manually quitting such apps one by one will be the trick to check for the culprit. It founds that BetterTouchTool is the problem.
Update: 10.11.5 will correctly prompt for administrator password and shows the blocking app.
OSX 10.11 introduced System Integrity Protection feature protecting the /usr/sbin folder, which will break existing miredo functionality to connect teredo tunnels.
Steps to fix it:
- Copy/move upgrade-migrated miredo command line tools from /Library/SystemMigration/History/Migration-XXX/QuarantineRoot/usr/sbin/ to /usr/local/sbin
- Edit /Library/LaunchDaemons/miredo.plist to use new /usr/local/sbin/miredo instead of /usr/sbin/miredo
- Re-enable miredo in prefpane
Since El Capitan also force kernel driver signing, if your tun/tap driver has problem to load, install the latest ones from here.
Just bought the latest Logitech MX Master mouse, which is quite powerful for Yosemite to natively support Mission Control and Spaces with its mouse gesture button, together with the interesting Smart Shift scrolling feature.
But also encountered the problem of pairing it with my MBP Retina on Yosemite 10.10.3. One discussion thread in the logitech forum suggested to delete all existing bluetooth devices to fix the connection. However, some hidden devices remain in the bluetooth paired list for Alt-Click menu. In this case, a complete bluetooth plist delete will finally help to pair the mouse with MBP.
Yosemite Bluetooth sometime freezes after wakeup, which then cannot be turned on/off and receive connections until reboot. If you want to manually restart it, do it by command line:
sudo kextunload -b com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport
sudo kextload -b com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport
Or you can use my Bluetooth Restart Alfred Workflow or similar AppleScript.
El Capitan UPDATE: Above bluetooth kext restart method will make the bluetooth driver unusable in 10.11, so restart your mac seems the only way to fix bluetooth freeze.
Just found some lagging when scrolling content in Chrome/Safari, especially after a few scrolls, the web page will pause about 0.5s then leap to the target position, which is quite annoying. After a few google around and testing, the Better Touch Tool v0.9995 is found to be the culprit. After disable it, all browsing returns smooth.
But as I use customized three finger swipes frequently, the magicprefs is now the alternative choice for gesture customization, which seems no conflict problem. But the system three finger swipe gesture must be disabled first in the trackpad preference pane, then the magic preference will enable the available gestures.
Just encounter a Yosemite system-wide problem of missing right click menu, but ctrl+click still works, which might be related to WindowServer process. Only reboot can get the right click back. After rebooting more than 10 times, it seems to happen after drag & drop to secondary monitor by bluetooth mouse. Quite strange, not sure if it’s bluetooth problem or drag&drop problem. Revert to Better Touch Tool temporally. And BTT released 1.0 which seems no lagging problem now.
Just encountered a frustrating problem when updating Numbers in the Mac App Store. There’s “an error has occurred” message in the Updates list as well as Purchased app list for Numbers after a seemingly success but actual fail update. Then, opening Numbers app will fail, showing an alert that the app is still updating. Go back to the MAS, the button for Numbers is now installed, so you cannot update/install the app ever again because App Store deems it alright.
Try deleting the Numbers.app in Application folder won’t help either. The “an error has occurred” is still there and the app status is always “installed” even the app is absent from my Mac. Logging out, and logging in to MAS several times, an error always occurred.
Now googling hundreds of pages. Try the interesting MAS debug mode solutions here, but the problem remains. Try the reset errors solution, still no hope. Even try the reset everything for app store cache solution and safari cache solution, both fails. And nothing going wrong for MAS in the Console even strongly suggested that it might be a MAS server problem, which would requires a bug report eventually. I supposed.
Finally, a non-sense post in somewhere in the piles of discussion threads on the web I’ve browsed gave a helpless cue and last resort action: changing the system language/location to English. The mysterious MAS problem is solved. The latest Numbers update showed and installed.
Now I advocate that a fallback App installer/updater mechanism should be there just in case that MAS goes wrong.