How often do you reinstall windows?


Recommended Posts

Back in the XP days, it always hit me with the getting-slower-with-time bug (or design deficiency, or whatever). I had to reinstall every six months or so. Tried imaging the hard drive back then, but discovered that after restoring from image, the softwares would be so out of date that it would hardly be an effort-saver. Since that realization, I use regular backup copies of my data for planned formats, but still maintain images for unplanned faults.

With Vista however, didn't feed the system get slow with time and never had to reinstall. By the time Windows 7 released, I was so used to a system that had everything set up in perfect tune with my needs that I wrestled with myself for about 3 weeks over whether or not to go through the hassle of cleanly installing Windows 7, and then spend eons setting it up the way I like it. Finally, Windows 7 won over my laziness.

i dont get it.

I think u dont need to reinstall windows after Vista came out.

yes i used to reinstall every 3months when i was on XP..

but my vista never slowed down.

i used my install for 3 years i think.

or so.

And i didnt install Windows 7 again either :)

Usually every six months or so. However on my Windows 7 machine i want to let it go a year or so just to see how well it holds up.

Same here.

Back in the XP days, it always hit me with the getting-slower-with-time bug (or design deficiency, or whatever). I had to reinstall every six months or so. Tried imaging the hard drive back then, but discovered that after restoring from image, the softwares would be so out of date that it would hardly be an effort-saver.

I feel the same way about imaging the install, plus it seemed like the image file would go corrupt while sitting on a spare hard drive, or the dvd it was on would mysteriously become unreadable just when I needed it.

I've since moved to using almost nothing but portable software so I never have to install or set up much of anything

Lifehacker did an article on this subject just days ago.

http://lifehacker.com/5435523/you-dont-nee...ndows-heres-why

While it's all good advice, and I've been doing it for years, in XP's case it doesn't matter as it still slows itself down over time no matter what the user does or doesn't do and the article fails to mention that.

Time will tell if the same holds true for Win7.

My god, please tell me that when you install a fresh system it is from a image backup? I didn't realize people actually do completely clean installs after a first round of installs with a new OS. I was creating a good image with core utilities and programs of the OS back in the Win2k days. I do for the most part understand a fresh install upon getting a new OS... not really sure if there is a benefit for service releases anymore though.

No kidding since the disk imaging was included in Vista. I have 3 machines that I have images of each computer with all the drivers and what not. All I have to do is run Windows update on my System and away it goes. On my Main machine I havent installed a fresh until Windows 7 hit RTM.

Once every six months usually.... Sometimes just cuz I'm bored...... :-p

I mean, i got my copy of 7 in September, and i JUST reinstalled it the other day, but only cuz I made a new bootable windows 7 USB key, and i wanted to see how much less time it would take to install it on my system (10 whole minutes less!)

If it wasn't for that, i would have had no reason to reinstall.

Used to be every year or so. The person saying you do it wrong if you do so, obviously forgotten how XP works. Unless you don't install anything, it becomes bloated - by design.

Now I have 2 computers side by side. A clean XP with only one purpose playing THE game I play, and a Linux machine for everything else and to keep all important files: musics, video, documents...

with my computers, re-installs are only done if absolutely necessary because i hate re-installing everything and getting used to a "new" Windows desktop. because lets face it, things are never quite the same as you had them before a format/install :(

As little as possible. My old XP/Vista setup lasted probably a good 4 years.

I only format when too much stuff starts to go wrong to the point of where its unfeasable time-wise to fix. Its an entire days work to do it on this machine and add back in the programs I need. I upgraded from Vista to Windows 7 on this machine to save time - but when 7 SP1 comes out I'll probably reformat.

a lot of people say they reformat with a new sp, but why?

do people upgrade sp every time is a fresh install?

why don't u just upgrade the sp, isn't that easier?

one thing I noticed when I upgraded sp, it took 4 hours!

a lot of people say they reformat with a new sp, but why?

do people upgrade sp every time is a fresh install?

why don't u just upgrade the sp, isn't that easier?

one thing I noticed when I upgraded sp, it took 4 hours!

Multiple reasons. In my case I create my own custom installation disc where I slip-stream the sp into the base installation, as well as the majority of the programs I use. Usually only takes a couple hours to reinstall everything.

Fire and forget....

original XP installation on my notebook that I bought it 5 years ago. Runs great without issue. On the desktop...the same install stays on until I upgrade the motherboard (every 3-4 years). Only exception being that I recently installed Win 7 on my XP desktop.

Personally I have never understood the whole reinstall every 6months to a year thing. If everything is running smooth then what is the point. During Win 95-ME days...I noticed a gradually degradation over time...but not post XP days

a lot of people say they reformat with a new sp, but why?!

A lot can go wrong with a SP. If you reinstall and then apply the SP it might be that there is less that can go wrong. At least, that was my thinking in the past when third party software was allowed to change system dlls. Now, it might not be true.

I have Windows 3.1 on an old 486 which is the original install.

I have Windows XP SP3 on a computer I built four years ago. I reinstalled once on that machine about two years ago.

I had Windows Vista on my laptop which was the original install until I reformatted it with Windows 7.

In my experience people seem to whine about their system performance after installing all their applications. They remember the increased performance when it was just a fresh install but as their apps start to pile on over the course of several months they see a degradation in performance. Many people don't even bother to shut off the services and start up items and opt to reinstall. Then of course there are the disorganized people who seemingly go out of their way to duplicate the functions of each program they have. Like I'll go on somebody's computer and see WinZip + WinRar + 7-Zip + PeaZip and wonder what the hell they are thinking. Finding multiple chat applications running is pretty common too. You'll have some poor fellow oblivious to the all-in-one chat applications running AIM, Yahoo, MSN, and some other service at the same time.

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

    • No registered users viewing this page.
  • 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!