Why is Windows ME unstable?


Recommended Posts

windows me unstable because, they did a crappy job!!!

God that was the worst experience I had, constant crashing, always some stupid errors popups out of no where, you have restart to get rid of it after restart you get BSOD  :cry:

:|

586665374[/snapback]

lol poor you. Thats bad though. Dont know why some had problems, and others. No problems at all.

Think about it from Microsoft's point of view. They knew that Me was the last in the line. The only parts of Me that would survive were the features that could be ported to the NT line (i.e. system restore, windows media player). Bug fixes to core components (e.g. kernel fixes) were largely gonna be thrown away after Me was released. Where would you spend your time?

Think about it from Microsoft's point of view.  They knew that Me was the last in the line.  The only parts of Me that would survive were the features that could be ported to the NT line (i.e. system restore, windows media player).  Bug fixes to core components (e.g. kernel fixes) were largely gonna be thrown away after Me was released.  Where would you spend your time?

586665399[/snapback]

Mental Health Clinic? lol

:laugh:

Actually, NO version of windows was unstable out of the box (for me, anyway).

It depends on what you do with it, what you install on it, how you mess around, etc.

For me, 9x installs usually screw up in half a year.

NT based installs don't screw up on me unless something stupid happens (like the power cutting out during a partitionmagic session)

Thankfully I only used ME for months, if not shorter due to Windows 2000 being in testing and at the time I was one the lucky ones that had 100% complete hardware support for the NT5.0/2000 betas.

However like many have said, Microsoft basically tried to do something to the 9x core that just couldn't be done anymore, too much old legacy code holding it down really. Thankfully there was another team already working on getting the consumers over to the NT core.

586585074[/snapback]

Windows 2000 professional (and I guess the whole family) was out months before windows me even came out. I remember I had bought it and ME came some months after. How was win2k in testing when ME was out?

  • 2 weeks later...

System restore on a DOS kernel, and the bad security of the poor kernel/filesystem. < that makes it unstable and insecure

turn off system restore and don't hook the pc to the internet. and don't install Norton garbage on it. makes it an ok OS

I tried installing it once (it was a clean install and not an upgrade), and oh no... Five minutes after starting the install process, the first BSOD appeared. The whole install process was an adventure. After about 20 BSODs and rebooting the system for another 20 times, I finished installing it.

Finally, ME worked for 10 days, with lots of problems and then completely crashed. I didn't use ME again and I won't ever. I prefer better DOS 6.1 than Windows ME.

The reason for all these problems (I think) is that Microsoft mixed Windows NT shell with Windows 98 Kernel, creating this awful mixture. I doubt if they had tested this operating system, before making it publicly available. :wacko:

Edited by nickg78

I have never had any problems with Windows ME. It's basically a revised version of Windows 98 and I installed it after it came out on my system. I ran it for years before I changed over to XP. (the first time I ran XP, I only had 64 MB RAM!). It was a wonderful experienced and it got me ready for XP. The only problems I had when runnig Me was common hardware driver failures (which was fixed after driver updates). But now I am on XP Pro.

Wow! Time has changed so far and we are using better software and hardware than what we used with Windows 98.

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!