Recommended Posts

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

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.

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.

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.

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....?

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.

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.

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...

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.

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 :)

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.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • 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
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!