Just tried it and it worked nearly perfectly. There was just a delay when I clicked on download before I saw the Run or Save menu pop up at the bottom. Then the same delay after clicking Run.
Otherwise, it worked as you would expect it to.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Windows Technical Preview (Windows 10) Bugs, Glitches and Good Things
- Thread starter S.B.G
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Otherwise, it worked as you would expect it to.
Huh. Maybe it's a bug that's carried over through all the updates? I dunno.
Thanks for trying it out.
Here's something I came across: Buildfeed.net
The build we got today might not be the final RTM release, just the first of the candidates. MS' internal builds go all the way up to 10503, so...who knows.
The build we got today might not be the final RTM release, just the first of the candidates. MS' internal builds go all the way up to 10503, so...who knows.
Can't wait to download the OFFICIAL MS Win10Prox64.iSO!
Updated the TH1 - 10240 in a VM! Working great and real snappy.
Cheers
Thanks for the link. I eventually got the new build but the metered connection problem still exists. The problem is that it only allows metered connections over wifi, not ethernet. I am using Windows 10 with Parallels and although my Macbook is connected via wifi, Parallels thinks that Windows 10 is connected via ethernet, hence no way of using a metered connection. I'm sure I'll find the answer eventually but so far, everything I've tried hasn't worked and Windows still tells me "we couldn't find wireless devices on this PC".
But here are 2 articles on verge saying 10240 is rtm:
http://www.theverge.com/2015/7/15/8974359/microsoft-windows-10-build-10240-testers
http://www.theverge.com/2015/7/15/8950481/microsoft-windows-10-rtm-date
And this is now rather confusing because on tenforums it says 10240 will expire on Oct 1, 2015.
http://www.tenforums.com/windows-10-news/1946-download-windows-10-insider-preview-iso-file.html
http://www.tenforums.com/windows-10-news/1946-download-windows-10-insider-preview-iso-file.html
"Has anyone managed to get a 27" iMac to display the native resolution of 2560 x 1440 using BootCamp yet?"
Yes, my iMac early 2012 had the the same problem, but after auto updates Windows found drivers for the AMD 6700 and updated to the native resolution. Win 8 EFI clean install with Usb Bootcamp drivers, after that used an ISO 10240 Build as an Update. Update found Broadcom BT Update as well, but a solution for the known issues with Audio HD in device manager. I think, we will have to wait half a year for updated Bootcamp drivers. Apple is known as slow as hell in this case, they don't want you to get a better impression for Win 10 than for Yosemite ;-).
Yes, my iMac early 2012 had the the same problem, but after auto updates Windows found drivers for the AMD 6700 and updated to the native resolution. Win 8 EFI clean install with Usb Bootcamp drivers, after that used an ISO 10240 Build as an Update. Update found Broadcom BT Update as well, but a solution for the known issues with Audio HD in device manager. I think, we will have to wait half a year for updated Bootcamp drivers. Apple is known as slow as hell in this case, they don't want you to get a better impression for Win 10 than for Yosemite ;-).
I Found This.
Though if I were to take a guess why it's happened to you now, it might have something to do with MS nulling all the current keycodes for the Insider Previews, and it maybe somehow messed you up in a roundabout way due to you running it in a VM. Worst case scenario, you'll have to wait until the 29th to get rid of it.
Thanks for the link.
I'm in El Capitan right now and the next time I boot back into my main Yosemite drive, I'll try out the suggestions in there.
In the mean time, a couple of days ago, I just created a local account and have been signing in with that.
That's good to know thanks.
I've since gone back to 8.1. Might give it another shot.
So just to be clear, do a clean install of 8.1 in bootcamp, install bootcamp drivers, install all the Windows updates. Then.. update to latest build of Win 10 and let it auto update again and I should be all good?
FWIW: I disabled the AUDIO HD features linked to my EVGA GTX-670-FTW-4GB, those caused MY audio problems in Device Manager. Never had any problems since with audio.
Good luck!
Cheers
to be clear
no need for a clean install at the first time, simply update from Windows 8 or 8.1;
the reason is, you have to update one time to get your Windows 10 for free, after that and Windows
is activated, you can do a clean install with an ISO (Build 10240 or newer).
My EFI install:
If you don't have the bootcamp drivers on an USb stick, create one with the bootcamp assistant
and let this stick connected to your Mac, while you do an clean install. It will automatically recommend
you to install the bootcamp drivers after Windows finshed the installation. I have done only an update
from a clean Windows 8 DVD install, without any further updates, directly updated to Windows 10 Build
10240 and it activated automatically.
Known issue with EFI, no sound and no sleep mode and the audio hd not found. My solution for sound
is an external usb soundcard.
no need for a clean install at the first time, simply update from Windows 8 or 8.1;
the reason is, you have to update one time to get your Windows 10 for free, after that and Windows
is activated, you can do a clean install with an ISO (Build 10240 or newer).
My EFI install:
If you don't have the bootcamp drivers on an USb stick, create one with the bootcamp assistant
and let this stick connected to your Mac, while you do an clean install. It will automatically recommend
you to install the bootcamp drivers after Windows finshed the installation. I have done only an update
from a clean Windows 8 DVD install, without any further updates, directly updated to Windows 10 Build
10240 and it activated automatically.
Known issue with EFI, no sound and no sleep mode and the audio hd not found. My solution for sound
is an external usb soundcard.
Well, if you are new for Windows, I can tell you a very simple thing:
Windows has fewer limitations, more customisation and more applications. You may compare it with Android. I mean, Windows and Mac OS X are like Android and iOS (We simply compare OS, not apps). Almost everything you are using not explicitly for Mac would likely find an alternative under Windows.
Unfortunately, of course, you need to treat with viruses, malware, ad-ware, system fixes, all of them. Thank you for Microsoft changing policy of releasing new version, in the future, user may only need to receive new build, containing bug fixes, feature enhancements, and various under-the-hood improvements, rather than dealing with the old troublesome, heavy, less flexible, and sometimes unstable Windows Update, and regular bug fixes every month.
If you have experience on using Windows, here is my preliminary experience:
Windows 10 is truly a brand new version of Windows, fine tuned. It migrates previous controversial Start screen inside new Start menu, creating a new universal, all-in-one-place start menu, for several things probably would do when starting using computer. I can use start menu to quickly access all programs installed, search for several small but useful utilities, control panel items, etc.
With new Task View (borrowed from Mac OS X mission control), I can simply see all apps I am running, either modern apps or traditional Win32 apps (Those modern apps are similar to apps downloaded from Mac App Store, while traditional Win32 apps are similar to apps downloaded outside Mac App Store, in concept level, though). There is one feature I like under Windows, is I can close programs I am running (at least program windows) right from Task View, while Mac OS X mission control cannot do that, even under El Capitan.
System performance has been greatly improved, especially from this most current build 10240. I may even miss startup screen if I am not aware of that because the startup speed is so fast under SSD. Overall system responsiveness has been improved greatly, according to my experience.
Backward compatibility is simply awesome. I have a game released in 1998. This game is surely an ancient game, but I can still run it under the latest 10240 build Windows 10 (64-bit), with some noticeable but tolerable graphical glitches! And some of my other apps released decades ago is still able to run, with little or no issue.
I cannot say this would help you much, although I hope this may give you a quick look at Windows 10, and the future of Windows.
Regards.
Just to clarify (even though most here know) is that Apple and Microsoft made a deal of sharing stuff back after their lawsuit, which is different than their negotiation for software and stock.
It really benefits the users on both ends. The Windows 7 superbar was heavily inspired from OSX Launcher/Launchy (can't remember the name). Rocketpad?
Though I'll admit I like the direction W10 took with UI. Though I wish the next major upgrade brings and option of some transparency like Mavericks/El Capitan.
I updated my VM (the one on El Capitan, copied from Yosemite) the other day to the latest build. After it finished, the display resolution is all messed up. Instead of 1680 x 1050 like OS X is using, I'm getting only these three options below.
I've reinstalled VMware Tools and that had no effect.
It seems to be using a generic display adapter set of drivers. I wonder if there is something more specific it should be using. (I haven't booted back into Yosemite to check what that VM is using yet).
That happened on 10.11 PB 1, and I've updated to PB 2 this morning with no change.
I've reinstalled VMware Tools and that had no effect.
It seems to be using a generic display adapter set of drivers. I wonder if there is something more specific it should be using. (I haven't booted back into Yosemite to check what that VM is using yet).
That happened on 10.11 PB 1, and I've updated to PB 2 this morning with no change.
In that screenshot.. the font rendering of Windows 10, wow it is baaad. What the heck was Microsoft thinking?
Great for you!
But seriously, while you may think subjectively that this is fine (and apparently you do) it's very easy to show objectively that the font in the screenshot is rendered in a very crude way.
This rendering technique is jaggie (objective) and is very high contrast to white (objective). Makes text more pixelated and inconsistent than on OS X (also objective)
Whether you like it or not is neither here nor there.