Upgrade to Win 8

By kiddingguy
in Microsoft (Windows)

 Share

Recommended Posts

Grand Master

kiddingguy

Posted
Posted

When Win 8 will hit Technet, I'm planning on upgrading one of my machines.

I noticed on the Dev.Prev. and TR that there is an upgrade option. The current Windows folder Will be renamed Windows.old

Can this folder safely be removed after the upgrade and migration of my data?

Or should this folder be kept at all times?

Link to comment
https://www.neowin.net/forum/topic/1096117-upgrade-to-win-8/
Share on other sites
Grand Master

kiddingguy

Posted
  • Author
Posted

So this is the right order??

1. Upgrade with keeping all data,

2. Check if data is still there with all shortcuts (like documents not in users\<...>)

3. When OK delete Windows.old

And in the case it still goes wrong:

4. Perform a clean Windows 8 install and install all your programs

The reason why I would do an instant upgrade - and not a clean install - is to check how this works, because I have never done this before. I guess I'm just a "clean install junkie". It's just in case when I upgrade my "main" computer to Windows 8 eventually I know the procedure.

This Windows 8 PC is just for daily basic usage, testing & work and in case something goes wrong there will be no damage to (important) files.... just the time to reinstall everything.

Rising Star

Andrea Borman

Posted
Posted

Well they say that Microsoft may only sell update DVDs of Windows 8. But when Windows 8 does go out on sale in the shops.I want to do a clean install of Windows 8,like I do when I install Windows 7.

They say on all of the Windows forums I have read that upgrade install causes too many problems. And that clean install is best. Andrea Borman.

Grand Master

articuno1au

Posted
Posted

Yes, but:

Personally I would suggest establishing a good backup system, formatting and going from clean.

Not to give Andrea's input any credence whatsoever; there are advantages to clean installs (mainly in neatness and install size) which make it worth while.

On top of this, having a good backup system means you can format, reinstall and be up and running in next to no time. For instance, my turn around time from format start to back fully installed and running is about 2 hours (I scripted an unattended install for office/visual studio etc).

It's a huge advantage if anything crashes/needs replacing or you get a virus you don't want to risk leaving on your system.

Grand Master

kiddingguy

Posted
  • Author
Posted

Yes, but:

Personally I would suggest establishing a good backup system, formatting and going from clean.

Not to give Andrea's input any credence whatsoever; there are advantages to clean installs (mainly in neatness and install size) which make it worth while.

On top of this, having a good backup system means you can format, reinstall and be up and running in next to no time. For instance, my turn around time from format start to back fully installed and running is about 2 hours (I scripted an unattended install for office/visual studio etc).

It's a huge advantage if anything crashes/needs replacing or you get a virus you don't want to risk leaving on your system.

True.

However, what's the deal with the install size of (the new) Windows folder?

Will the old folder just be renamed Windows.old and a new one created and installed in?

The itchy part is the registry I guess.... (neatness)

Basically you are just saying... do a clean install and I'm better off in the long run?

Like I said, the progams used on my notebook - and which are to be installed afterwards - are not that much. Just some Office applications and browsers and other productivity software, like Adobe, Diskeeper etc.

EDIT:

Windows 8 has a new file system right? Windows ReFS.

I guess with an upgrade I'd still stick to the NTFS file system of Windows 7 and have Windows 8 as primary OS on NTFS. This could cause some (major) problems - maybe.

So a clean install is preferred. At least I think so....?

Grand Master

neo1911

Posted
Posted

Most people are confused when we say Upgrade to Windows 8

1. Upgrade to windows 8 by clean install

2. Actual upgrade by keeping programs, settings, files, etc.

3. Mix of above two by keeping all old operating system data in windows.old folder.

Any other upgrade scenario?

@ OP

Make sure you have restored save games, program settings, and documents, music from the windows.old folder. If you don't require any of the data in Windows.old, you can delete it.

Collaborator

SledgeNZ

Posted
Posted

The other option is to convert your current machine into a VM. You can use disk2vhd (Available from MS) and then run your original setup via hyper-v in win8.

You need to check that your machine supports hyper-v prior to doing all of this though.

At the very least you'll be able to mount the virtual hard drive of your previous install under win8 and copy anything off it that you need.

Grand Master

articuno1au

Posted
Posted

True.

However, what's the deal with the install size of (the new) Windows folder?

Will the old folder just be renamed Windows.old and a new one created and installed in?

The itchy part is the registry I guess.... (neatness)

Basically you are just saying... do a clean install and I'm better off in the long run?

Like I said, the progams used on my notebook - and which are to be installed afterwards - are not that much. Just some Office applications and browsers and other productivity software, like Adobe, Diskeeper etc.

EDIT:

Windows 8 has a new file system right? Windows ReFS.

I guess with an upgrade I'd still stick to the NTFS file system of Windows 7 and have Windows 8 as primary OS on NTFS. This could cause some (major) problems - maybe.

So a clean install is preferred. At least I think so....?

The install will only gain a couple of gb (at a guess) but it's the small things like finding backed up profiles with random names, backed up program settings etc etc that when you are browsing your files just annoy the hell out of you.

The same thing is true of the registry. There'll be tons of changes between the system. I just think that you are better off avoiding having to clean up by starting clean >.<

It's purely a personal choice thing. I've "upgraded" a dozen machines and the users have had no problems whatsoever.

Windows 8 doesn't allow you to use ReFS. It's currently only available in Server '12 (just like NTFS was when it was released) with client support likely coming by Windows 9.

Both answers are completely viable. I just like clean installs :p Worst that happens is you run an upgrade, decide it ****es you off too much and then do a clean install.

The only consistent piece of advice between both scenarios is make sure your backup is solid >.<

  • 2 weeks later...
Grand Master

BajiRav

Posted
Posted

Any experiences with this so far?

I had upgraded a 13+ month Windows 7 install to Windows 8 RP and the system performance was pretty much same as what I have now (with a clean install at RTM). I had few minor issues but I think they were unrelated.

Collaborator

brlmedia

Posted
Posted

this is a question that will be debated for ages lol. I personally have cleaned installed the RTM on 2 machines, one hour I was back up and running. have tested 2 upgrades as well, just seemed to have "junk" I didn't need or want.

whatever you decide, have your data backed up. product keys, your favorites folder, etc. you will thank yourself :)

Grand Master

Nothing Here

Posted
Posted

EDIT:

Windows 8 has a new file system right? Windows ReFS.

I guess with an upgrade I'd still stick to the NTFS file system of Windows 7 and have Windows 8 as primary OS on NTFS. This could cause some (major) problems - maybe.

So a clean install is preferred. At least I think so....?

ReFS? Then why is my disk still NTFS when I did a clean install?

This topic is now closed to further replies.
 Share
Go to topic listing

  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones

      By zikalify · Posted

      Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • Microsoft confirms Recycle Bin bug across all versions of Windows

      By snowy owl · Posted

      I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs

      By hellowalkman · Posted

      Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • My favorite file manager for Windows 11 finally gets a long-requested feature

      By Malisk · Posted

      And with SO much better perf than the laggy mess that is Files.
    • The official Funny Pictures thread

      By Steven P. · Posted

  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done

  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!