Recommended Posts

This really is a non-issue. As has been said many times, all versions of Vista are included on the DVD, including Full Retail and Upgrade. So you'll be able to boot from the CD no matter what. If for some reason Microsoft doesn't allow you to use your upgrade key during a clean install (which doesn't make sense - they will, but if they didn't) just don't input a key, choose the correct version of Vista, and let it install.

After installation is complete, input you upgrade key and activate windows. Bam, no mess, little fuss.

This really is a non-issue. As has been said many times, all versions of Vista are included on the DVD, including Full Retail and Upgrade. So you'll be able to boot from the CD no matter what. If for some reason Microsoft doesn't allow you to use your upgrade key during a clean install (which doesn't make sense - they will, but if they didn't) just don't input a key, choose the correct version of Vista, and let it install.

After installation is complete, input you upgrade key and activate windows. Bam, no mess, little fuss.

Won't work.

When you install Vista it does a license verification to make sure that the key you are using is being used properly. So you can't just toss in the key during an install or after a clean install using the activation wizard.

The only way to get it to work is through XP. You have to have XP installed and then when setup runs enter the key as it's going to check the XP license to make sure it's valid. It's all controlled by product key based locks.

Won't work.

When you install Vista it does a license verification to make sure that the key you are using is being used properly. So you can't just toss in the key during an install or after a clean install using the activation wizard.

The only way to get it to work is through XP. You have to have XP installed and then when setup runs enter the key as it's going to check the XP license to make sure it's valid. It's all controlled by product key based locks.

Right. And if you don't enter a key during setup, there's no way this product key lock can kick in. Once Vista's installed, it doesn't care if your Key is OEM, upgrade, or whatever as long as its valid.

Right. And if you don't enter a key during setup, there's no way this product key lock can kick in. Once Vista's installed, it doesn't care if your Key is OEM, upgrade, or whatever as long as its valid.

Are you absolutely sure? Is there some reason why the activation wizard in Vista can't exclude all upgrade keys? The email from MS certainly seems to indicate that this must be the case (either that, or the upgrade DVDs are not the same as the retail DVDs). If you could do as you suggest, then the information given by MS in that email is simply untrue.

Also, am I eligible for an upgrade from XP OEM, or XP x64 OEM? If so, then it would be kind of problematic if you have to activate the XP install before upgrading to Vista, since the OEM version of XP should not be activated on a new PC, while I am assuming that the upgrade version of Vista has just as liberal a license as the retail version? Hope someone can be bothered to clarify this for me :)

I'm still thinking that people is discussing this without a real confirmation. Something like this would mean changing the license terms of the upgrade versions of vista. When are those EULA's coming??

What do you mean when is the EULA coming? The EULA is already in Vista during setup :blink:

Also y_notm, you have no idea about what Product Keys are do you?

They are just that, KEYS

Each key can only perform a certain task.

Why do you think you can't install an unmodified retail XP CD with a Corporate Key and have it work?

Because in that case, the key doesn't fit the lock ;)

Why do you think you can't install an unmodified retail XP CD with an Upgrade Key and have it work?

Once again, the key doesn't fit the lock

Let me give you a good explanation here. That key when entered determines what type of product you are going to be installing/activating.

If you skip the key then the key that it chooses to use is a Retail Evaluation Key. That gives you 30 days of functionality to get a good valid key going.

Now what happens when you go to activate that copy and it detects that you're using an upgrade key (and yes the keys are specific) without having done an validated upgrade?

You've guessed it. It will then ask you to verify your license which will require you to validate your previous license in which case without one you will be stuck.

Replies inline

What do you mean when is the EULA coming? The EULA is already in Vista during setup :blink:

Also y_notm, you have no idea about what Product Keys are do you?

They are just that, KEYS

Each key can only perform a certain task.

Why do you think you can't install an unmodified retail XP CD with a Corporate Key and have it work?

Because in that case, the key doesn't fit the lock ;)

That was the case with XP, but Vista is different. All versions are on one CD, so you can use any legit key on any Vista CD and it will automatically install the version that matches that key.

If you skip the key then the key that it chooses to use is a Retail Evaluation Key. That gives you 30 days of functionality to get a good valid key going.

Now what happens when you go to activate that copy and it detects that you're using an upgrade key (and yes the keys are specific) without having done an validated upgrade?

You've guessed it. It will then ask you to verify your license which will require you to validate your previous license in which case without one you will be stuck.

First part, true. Second part, I'm not so sure of. From what I know of activation (and maybe this changed with Vista, but this was the case with XP) the activation servers just check that the key itself is a valid Vista key and that its not currently activated on another computer, then says "OK you're activated." There is no check to validate you've done an upgrade. In other words, activation doesn't care how you get there as long as you have a valid key.

In XP's set up (again, going by this because we don't have Vista upgrade keys yet) you pop in the 2000 or whatever CD during the clean install and it verifies you have the media, it doesn't connect to the internet to tell MS you indeed have a qualifying previous version and it doesn't flag your installation in any way, it just allows installation to continue. At the end of the install, your clean install with an upgrade disk looks exactly like a clean install with a full version disk. Therefore, whether you clean installed or upgraded has no impact on Activation.

Also, the privacy policy says nothing about sending upgrade version status to Microsoft during Activation, only the key, IP address, and hardware hash.

Edited by y_notm
Replies inline

That was the case with XP, but Vista is different. All versions are on one CD, so you can use any legit key on any Vista CD and it will automatically install the version that matches that key.

First part, true. Second part, I'm not so sure of. From what I know of activation (and maybe this changed with Vista, but this was the case with XP) the activation servers just check that the key itself is a valid Vista key and that its not currently activated on another computer, then says "OK you're activated." There is no check to validate you've done an upgrade. In other words, activation doesn't care how you get there as long as you have a valid key.

In XP's set up (again, going by this because we don't have Vista upgrade keys yet) you pop in the 2000 or whatever CD during the clean install and it verifies you have the media, it doesn't connect to the internet to tell MS you indeed have a qualifying previous version and it doesn't flag your installation in any way, it just allows installation to continue. At the end of the install, your clean install with an upgrade disk looks exactly like a clean install with a full version disk. Therefore, whether you clean installed or upgraded has no impact on Activation.

Also, the privacy policy says nothing about sending upgrade version status to Microsoft during Activation, only the key, IP address, and hardware hash.

Once again y_notm you're not listening.

When you try to install Vista it detects what key you are using and then determines what you can or cannot do.

If you boot the system and try a clean install using the upgrade key it will tell you that you cannot continue.

I've already said all I have to say on this subject and this is my last post on it as I will not waste my time further arguing a point on which I know I am correct.

But you're not correct because you never read my first post complete: You don't need to provide a key for Windows Vista to complete installation. It can be provided after installation. You simply choose which version you want to install in that case.

This isn't something new and mindblowing, and its still present in RTM. In fact, thats how MS advised testers to install RTM - they provided the CD image almost 2 full weeks before keys were sent out.

If for some reason you need more proof of this, here's a couple of screens.

post-821-1166303204_thumb.jpg

post-821-1166303302_thumb.jpg

Edited by y_notm
  • 3 weeks later...
But you're not correct because you never read my first post complete: You don't need to provide a key for Windows Vista to complete installation. It can be provided after installation. You simply choose which version you want to install in that case.

This isn't something new and mindblowing, and its still present in RTM. In fact, thats how MS advised testers to install RTM - they provided the CD image almost 2 full weeks before keys were sent out.

If for some reason you need more proof of this, here's a couple of screens.

Read my prior posts and you will see that I did actually read yours fully.

I understand what you are saying but you're still not getting it. YOU DO NEED TO PROVIDE A KEY. Even if you don't enter one there is a default key that Vista already has included in it's code that allows the installer to continue. If you don't believe me check with any software you want that can give you your product key and you will see that I am correct.

That default key allows for an install, but not for activation. When you then attempt to activate it will tell you that you need to enter a new key. Once you enter in that key the server will reject it because it is an upgrade key and is not being used in an upgrade scenario.

It can tell from the default install key that you did a clean install first and that the key that you are attempting to use is not valid for the purpose which you are attempting to use it for and will reject it.

You can argue with me all you want, but the fact of the matter is I'm right, you're not.

I mean come on the proof is right in your second screen shot.

"If you choose not to enter the product key now, you might need to reinstall Windows later and potentially lose data, information, and programs, or you might need to pu rchase another edition of Windows Vista."

Now let's read that logically.

If you do not enter the product key, you might have to reinstall and lose things if you run out of time before you enter the new key, OR if the keys is not for the version you are installing.

If you chose a full VERSION, note that, VERSION, install then the upgrade VERSION key WILL not activate it as it uses slightly different PID bits.

I mean come on what kind of morons do you take MS for?

  • 4 weeks later...
Hello, Here is an update on your inquiry about Windows Vista Ultimate. Please accept our apologies for the delay in our response. WinSAT is available in all editions of Windows Vista. It is true that the upgrade to Windows Vista can only be run from inside Windows XP. The Windows Vista product group has also provided the following information about how this works. a. Recovery on a true bare metal system (formatted disk, no system installed) requires a PSS call, there is no way to use retail media on a boot from media install. PSS has the infrastructure to help customers in this case. b. If you want to install from retail media without a PSS call, yes you?ll have to reinstall Windows XP, then upgrade to Windows Vista. c. In the case where setup fails we have implemented rollback, something we didn?t have for Windows XP - a failed upgrade will simply return the machine back to Windows XP.If you choose to clean install from Windows XP, with a failure, the OS will also roll back. e. Windows Vista never really ?Erases? Windows XP until you have successfully reached the new desktop. f. If you need the ability to clean instbare metal systemstems, you must buy the full product package, not the upgrade edition. Should you have other quiestions, please feel free to write back. Did I completely answer your question? Please let us know by replying to this message. Thank you

1. Clean installs from XP... POSSIBLE!

2. Clean installs with an UPGRADE key by booting the disc. NOT POSSIBLE.

Windows Vista never really ?Erases? Windows XP until you have successfully reached the new desktop

I'd like to know what "erases" actually means. If I clean install from XP on the same partition, will any part of XP still be on the disk? Wouldn't that defeat the purpose of a 'clean' install?

Seems like a bit of a chore, but if you want to save money on the upgrade version you'll have to make sacrifices.

Only if you're a builder. And then the only sacrifice is the extra half hour it takes to install XP first, and then move on to installing Vista.

For most of the mass market, they won't ever format their HDD after an initial clean install (if they even choose a clean install) - they'll be perfectly fine just purchasing an upgrade edition and putting the CD into their machine that already has XP installed on it, and they won't have any problems.

-Spenser

Only if you're a builder. And then the only sacrifice is the extra half hour it takes to install XP first, and then move on to installing Vista.

Half an hour? It takes longer than that, plus you have to be present several times during the install; then you need to activate it. That is a real inconvenience, particularly if doing it more than once.

Half an hour? It takes longer than that, plus you have to be present several times during the install; then you need to activate it. That is a real inconvenience, particularly if doing it more than once.

Eh, half hour tops. Most of the updates can be slipstreamed into XP prior to installation (Most system builders do this for normal XP installs, the now 6 .NET installs/upgrades are the only hassle), the only "hands on" moments are the CD key for XP, then the activation (which if you slipstreamed the drivers for the most popular NICs, no biggy) which is done directly after/during install.

Granted it slows down production time ALOT. But then, that's what you get for being cheap and only buying an upgrade *shrugs*

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • We have disabled advertising in the forums for now for an undetermined period. If you feel like you get a lot of value out of the site please do whitelist ads on the news articles, and/or consider getting a subscription, we offer two tiers, one at: $14 per year (support the site for just over a dollar a month) or the $28/year tier (just over $2/month) that disables advertising and affiliate link tracking throughout the site (so also on the news side). We also have a 'Buy us a coffee' page if you just want to make a one-time donation. I am not mincing words when I say it is becoming harder and harder to monetize publications like Neowin, it's a fact of life that when we can no longer afford to pay for everything we'll go like many other sites already have. It doesn't have to cost you anything There are other ways to support Neowin too, like posting on topic content in the forums (technical support/questions/helping others) and sharing our news articles.. this costs nothing but your time and is just as important as subscribing or making a monetary donation! Anyway thanks for your time and continued support of Neowin. Now in our 26th year, and hopefully many more! For all the lurkers out there that whitelist us, make a free member account, and see fewer (only inline) ads on the news side  
    • BATorrent 3.0.2 by Razvan Serea BATorrent is a lightweight, open-source BitTorrent client built with modern C++ and Qt 6, offering a clean, fast, and privacy-focused alternative to traditional torrent apps. It supports magnet links, .torrent files, resume data, sequential downloading, per-file priorities, and even imports from qBittorrent. Power users benefit from integrated RSS auto-download with regex filtering, duplicate detection, and automatic tracker lists from Stremio. Streaming is seamless thanks to auto-detected players like VLC and IINA. BATorrent includes robust VPN tools—interface binding, auto-detection for WireGuard-based services like Mullvad and NordLynx, kill switch, proxy support, and IP filtering. A full WebUI enables remote control, while integrations with Plex, Jellyfin, and Emby automate library updates. With themes, speed scheduling, system-tray alerts, and cross-platform support for Windows, Linux, and macOS, BATorrent delivers a polished, high-performance torrenting experience. BATorrent features: Core .torrent file and magnet link support Resume data — picks up where you left off after restart Import torrents from qBittorrent Create .torrent files from any file or folder Sequential download mode Per-file priority control (skip, low, normal, high) Seed ratio limits with auto-pause DHT, PEX, UPnP, NAT-PMP RSS Auto-Download Subscribe to RSS feeds — automatically download new torrents as they appear Regex filters — match only what you want (e.g. 1080p|720p, S01E\d+) Per-feed settings — custom save path, check interval (5–1440 min), enable/disable Auto-download — matched items are downloaded automatically in the background Supports magnet links, .torrent URLs, and tags Tray notifications when items are auto-downloaded Duplicate detection — never downloads the same item twice Stremio Stremio Addon System pre-installed — works out of the box Auto tracker list from ngosang/trackerslist Streaming Play while downloading — stream video files before the download is complete Supports mp4, mkv, avi, mov, wmv, flv, webm, m4v, ts Auto-detects installed players (VLC, IINA, system default) VPN & Privacy Interface binding — lock torrent traffic to a specific network interface (e.g. tun0) Auto VPN detection — identifies VPN interfaces (tun, tap, WireGuard, Mullvad, NordLynx, ProtonVPN) Kill switch — automatically pauses all torrents if the VPN interface drops Auto-resume — resumes only the torrents paused by the kill switch when VPN reconnects Proxy support — SOCKS5 and HTTP proxy with optional authentication IP filtering — load P2P blocklists to block unwanted IP ranges Protocol encryption (enabled / forced / disabled) WebUI Remote management — control torrents from any browser at http://localhost:8080 REST API with JSON responses Add torrents via magnet link or .torrent upload Pause, resume, remove torrents remotely View peers and files per torrent Dark theme matching the desktop app HTTP Basic Auth with SHA-256 password hashing Configurable port and remote access (localhost vs 0.0.0.0) Interface 3 themes: Dark, Light, Midnight (bat/vampire aesthetic) Real-time speed graph Detailed panel with tabs: General, Peers, Files, Trackers Filter bar: search by name, filter by state (Active, Downloading, Seeding, Paused, Finished) Drag & drop .torrent files and magnet links Drag & drop reorder in torrent list System tray with notifications (download complete, kill switch events, RSS auto-downloads) Splash screen with bat animation Bilingual: English and Portuguese (BR), auto-detected from system locale Bandwidth Scheduler Alternative speed limits — set different download/upload limits on a schedule Time range — configure active hours (e.g. 01:00 to 07:00), supports overnight ranges Per-day control — choose which days of the week the schedule applies Automatically switches between normal and alternative speeds Media Server Integration Plex — automatically trigger library scan when a download completes Jellyfin / Emby — same automatic library refresh via API Configure server URL and authentication token/key in Settings System Cross-platform: Windows, Linux, macOS Auto-shutdown — automatically shut down PC when all downloads complete (60s cancellable countdown) Auto-update system (AppImage on Linux, installer on Windows, DMG on macOS) CLI arguments: pass .torrent files or magnet: URIs directly Keyboard shortcuts: Space to toggle pause, Ctrl+A to select all, Ctrl+O to open BATorrent 3.0.2 changelog: Phone pairing & WebUI The browser WebUI was reskinned to match the desktop app — same dark palette, Inter font, flat surfaces, the real BATorrent logo (it was a random bat before), and a proper magnet icon. It now looks like the same product, not a separate dashboard. Pairing is one tap and zero typing: the generated WebUI password is now copyable, and the QR code carries the credentials — scanning it from your phone logs straight in (no typing the IP or password), then drops the credentials from the address bar. Search Two new providers: RuTor (CIS sources, no login, via a public TorAPI relay) and Torrents-CSV. Results are sorted by seeders (healthiest first), and each search now times out after 15 s so one dead provider can't hang the UI. Files & trackers Per-file priority is back: right-click a file in the detail panel to set Skip / Low / Normal / High. Rename an individual file inside a torrent (double-click or the file menu), separate from renaming the torrent. Remove a tracker from a torrent (the ✕ on a tracker row); adding was already there. Smart Paste on Ctrl+V — paste a magnet, a 40-char info-hash, or a .torrent URL straight from the clipboard and it's added immediately (text fields still paste text normally). Covers & titles Anime fansub naming ([Group] Title - NN) now resolves to the right show. Audio channel layouts in titles (DDP5.1, 7.1, …) are stripped so they don't pollute cover matching. Under the hood The legacy QWidget interface is gone. QML had been the only UI since 3.0.0 (reachable old code lived behind a hidden --legacy flag); with parity confirmed, the entire QWidget layer — main window, every dialog, the theme manager — was removed (~13,400 lines). The four restored actions above were features that backend already supported but the QML port had never wired. macOS: the WebUI password hash moved out of the keychain into app settings, so launching the app no longer pops a login-keychain password prompt on unsigned builds. The actual password still lives in the keychain. Cleanup: ~400 orphaned translation strings and a batch of dead code removed; internal duplication collapsed; an ARCHITECTURE.md added for contributors. Unit / security / memory tests and the ASan/UBSan/TSan sanitizers stay green. Download: BATorrent 3.0.2 | 30.5 MB (Open Source) Download: BATorrent Portable | 42.3 MB Links: BATorrent Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • How about a global switch to turn the awful things off instead of a registry hack? Then everyone wins.
    • This doesn't strike me as so shocking when... " IT admins do have some control over this rollout. If they choose to opt out, devices in their tenant won't automatically get the dreaded Copilot app"
  • Recent Achievements

    • Mentor
      grik went up a rank
      Mentor
    • Dedicated
      JKR earned a badge
      Dedicated
    • One Year In
      CHUNWEI earned a badge
      One Year In
    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      475
    2. 2
      PsYcHoKiLLa
      262
    3. 3
      Skyfrog
      79
    4. 4
      ATLien_0
      60
    5. 5
      FloatingFatMan
      60
  • Tell a friend

    Love Neowin? Tell a friend!