Recommended Posts

Is anyone running fine with doing an upgrade? Just seems unbelievable to me that in 2012 we're still having to do clean installs.

I did an upgrade install and haven't hit any major snags yet. I locked up the App Store while it was downloading updates because I put my Mac to sleep which was odd... I haven't tried to repeat it, may have just been a fluke. Other than that my computer feels very snappy. It is at least as snappy as it was w/ previous Lion installed, if not a little snappier. So I'm satisfied with the upgrade and probably won't do a clean install.

If you are upgrading from Snow Leopard you might want to do a clean install.

Is anyone running fine with doing an upgrade? Just seems unbelievable to me that in 2012 we're still having to do clean installs.

I upgraded from Lion on both my Retina MBP and 27'' iMac, despite the fact I normally do clean installs. Both work fine and feel as fast (if not faster) than Lion did on the same hardware.

Also glad to see iWork got an update to take full advantage of the Retina Display.

My upgrade completed fine, no issues here. Well, other than Minecraft not being codesigned....

Same with a few other apps I use, I had to disable it for now, hopefully more and more apps will be signed in the future so I won't need to have it disabled!

Same with a few other apps I use, I had to disable it for now, hopefully more and more apps will be signed in the future so I won't need to have it disabled!

The few apps that you have can be manually bypassed without having to turn off gatekeeper completely

The few apps that you have can be manually bypassed without having to turn off gatekeeper completely

Really? There is a way to manually bypass gatekeeper?

Aside from a more polished feel from Lion, most apps seem to work fine, but only if I completely disable gatekeeper. SkyDrive is the only one that complains about unable to access KeyChain, but there is a workaround for it.

From 2010 MBP 15" battery tops out at 2 hours under Mountain Lion, as opposed to 2 and half under Lion... as opposed to 6 hours under Snow Leopard.. (all with SMC reset)

Control-click or right click the app, and select Open.

http://support.apple...US&locale=en_US

Oh that is good, so basically now I had it off, if I enable it those non-signed apps will continue to work because I have already opened them? (until maybe they update but by then should be signed anyway)

Oh that is good, so basically now I had it off, if I enable it those non-signed apps will continue to work because I have already opened them? (until maybe they update but by then should be signed anyway)

Yes they'll continue to work, but I think you'll need to enable them (using the method I previously described) after turning Gatekeeper back on.

The thing is though, Apple doesn't support clean upgrades anymore. That isn't their official way of doing it. Right now we can still go inside and boot the installer but in a future scenario we may not be able to do that anymore, then what? We will all be doing upgrades eventually.

Also I just did a clean install of Lion like 2 months ago I barely had anything installed at all. Photoshop was like the only app which I've actually had to install all my other apps were just drag and drop to the apps folder. I've thus done no customization of anything and I was running the latest Lion update before upgrading.

Anyway everything is fixed now so I'm happy.

+Vice:

They can't get rid of "Clean Install" procedures. What if your Mac hard drive died and you had to get a new one? What are they going to do then? Force you to install Lion first so that you can then install the Mountain Lion upgrade? I don't think so.

"Clean Installs" will always be there. They say Macs for the most part don't need to be restarted after installing stuff but I always do it anyways just in case. Also, Circaflex is right, if you do an "upgrade" then you should also do a "repair permissions" thing just to make sure everything is in place.

The thing is though, Apple doesn't support clean upgrades anymore. That isn't their official way of doing it. Right now we can still go inside and boot the installer but in a future scenario we may not be able to do that anymore, then what? We will all be doing upgrades eventually.

What if the world ends tomorrow, then what?

What you're saying makes little sense really. The ability to do a clean install always needs to be there. If only when you install a new HDD in your Mac or in the scenario your entire system gets corrupted due to whatever reason.

I don't think they will let you do a clean install eventually using the App Store download. I think the only way you'll be able to do it eventually is by using the recovery partition after already installing the latest OS release as an upgrade (To get the recovery partition in place). Which answers your question .Neo as to how they would handle HD Death.

I don't think they will let you do a clean install eventually using the App Store download. I think the only way you'll be able to do it eventually is by using the recovery partition after already installing the latest OS release as an upgrade (To get the recovery partition in place). Which answers your question .Neo as to how they would handle HD Death.

How is that scenario any different from today's? The way you do a clean install right now is by extracting the recovery partition image from the updater, restore it to a USB stick, boot from it, wipe your HDD and reinstall. The recovery image has to remain there somewhere in the updater package otherwise it can't be put in place to begin with.

What you're fearing became last year's reality, yet I continue doing my erase & installs just fine.

How is that scenario any different from today's? The way you do a clean install right now is by extracting the recovery partition image from the updater, restore it to a USB stick, boot from it, wipe your HDD and reinstall. The recovery image has to remain there somewhere in the updater package otherwise it can't be put in place to begin with.

What you're fearing became last year's reality, yet I continue doing my erase & installs just fine.

I'm not fearing anything. I did an upgrade and not a clean install, I don't do clean installs. I want them to make the upgrade system the most reliable there is because that is the way we should be upgrading our systems. Clean installs is something Windows users should have to deal with, not us on OS X. Our OS is supposed to be easier.

But again in future I foresee the OS becoming more compartmentalized in to a series of individual updates and the notion of purchasing the OS or even receiving a whole bunch of updates in one go (like a major OS update) will be a thing of the past and instead incremental updates more akin to .1 point releases will become the norm. That is where I foresee Apple taking us and at that point clean installs will not be possible you'll only be able to reset the machine back to the base OS from a few years ago and then after the install is completed a large update download will begin with all the changes since then to current day.

Turning OS X Releases more in to service packs is I think the avenue they will take.

I'm not fearing anything. I did an upgrade and not a clean install, I don't do clean installs. I want them to make the upgrade system the most reliable there is because that is the way we should be upgrading our systems. Clean installs is something Windows users should have to deal with, not us on OS X. Our OS is supposed to be easier.

But again in future I foresee the OS becoming more compartmentalized in to a series of individual updates and the notion of purchasing the OS or even receiving a whole bunch of updates in one go (like a major OS update) will be a thing of the past and instead incremental updates more akin to .1 point releases will become the norm. That is where I foresee Apple taking us and at that point clean installs will not be possible you'll only be able to reset the machine back to the base OS from a few years ago and then after the install is completed a large update download will begin with all the changes since then to current day.

Turning OS X Releases more in to service packs is I think the avenue they will take.

They will never abandon SIU, NB, NR. It's half the feature of their EFI setup. I completely disagree with you and you're only looking at it from a "consumer" view. They use too many tools for their own deployments to abandon these methods.

I did an upgrade, that is the route I have taken with all of the prior OS X releases that have allowed you to do so and never had any issues.

So far I had a really weird issue where I checked out Airplay Mirroring with my Apple TV (I have a 2011 Pro that is compatible, and it worked, was a little wonky but worked, and I turned it off after about 2 minutes. Did some other stuff, ate dinner, come back to my laptop, resumed from screen saver to find the desktop at some weird low resolution. like 1152 I think it was. Was not filling up the screen, just looked like utter ass. Went into Display settings, and nothing I did would get out of it. I would click an every display option to just have it do nothing. Was stuck at this craptastic resolution.

Restarted and all was back to normal, but definitely was not digging it. About to verify and repair my permissions then disk if need be, have not done that yet, but really hoping this does not wind up being the first time I regret going the upgrade route.

This topic is now closed to further replies.
  • Posts

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol. The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Most of the stuttering can easily be fixed by generating a PSO cache and compiling every shader before loading the game, it's up to the developer to set it up properly.
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!