3 new performance and reliability updates for Windows Vista


Recommended Posts

Installed the x86 versions on my lappy, and all is well. Hopefully this will improve battery life in Vista, as with Ubuntu I get about 3 hours per charge. Under Vista I've only been getting 2.25 hours max. Maybe this will help. =)

failed and what else does it say? Are you downloading the x86 or the x64 version but applying it to the wrong type of machine?

That's the problem. It only says failed. I have some knowledge of computers, so I wouldn't make the mistake of downloading the wrong version. I'm trying to install the x86 version on my x86 machine.

I've made a screenshot and translated the text. That's all it says. This dialog dissapears automatically and a somewhat identical one appears saying that the update was not installed. No explanation whatsoever.

post-238458-1191520256.jpg

i installed all 3 updates, restarted, now my PC won't even POST... i looked in the motherboard manual, and it says:

memory detect test

testing onboard memory size. The D-LED will hang if memory medule is damaged or not installed properly.

wtf.. how can my ram be bad after it worked fine for 2 years?

Just an update on my situation.

After the updates installed, the screen went black after I heard my PC rebooting.

I watched in amazement as my screen stayed black with nothing to display for a few minutes. I disassembled my PC (removed HDD, cables, and the video card, and all 4 sticks of ram).

I left it unplugged for a few minutes, hooked it up to another monitor, and it booted (with 1 stick of ram and 1 video card).

I proceeded to place everything back in one at a time, and booted accordingly, then with everything back in, it booted up fine.... weird huh.

Note: This update was hell, and I see no performance improvements for start up, but I do notice a massive increase in TIME to boot.. Yes, it actually takes longer to boot now.

Edited by lylesback2
That's the problem. It only says failed. I have some knowledge of computers, so I wouldn't make the mistake of downloading the wrong version. I'm trying to install the x86 version on my x86 machine.

I've made a screenshot and translated the text. That's all it says. This dialog dissapears automatically and a somewhat identical one appears saying that the update was not installed. No explanation whatsoever.

post-238458-1191520256.jpg

Start -> Run, then paste this in.

%windir%\Windowsupdate.log

Find the entry for the failed update and there will be an error code. You can find it easy by doing a search for "Error". It will be in the format "Error #x########" for example "Error 0x80190194". Report back with the error code.

i installed all 3 updates, restarted, now my PC won't even POST... i looked in the motherboard manual, and it says:

wtf.. how can my ram be bad after it worked fine for 2 years?

if it didn't post, it's not an operating system related problem

Well I have no benchmarks ect but from my limited observation after one or two boots it felt to me that the time to go from the login to a useable desktop with everything loaded had improved pretty significently but at the same time it also felt a bit slower to get to the login screen from power on.

I can't really say but and thats just my gut feeling. For all I know nothing has changed. I know they installed fine however.

Hmm, those with problems: do you happen to have VirtualBox installed? I've already ruled out Daemon Tools (uninstalled, tried to patch, didn't work), and VBox seems to be the only thing that could have an effect, if it's any 3rd party program and not the drivers.

Hmm, those with problems: do you happen to have VirtualBox installed? I've already ruled out Daemon Tools (uninstalled, tried to patch, didn't work), and VBox seems to be the only thing that could have an effect, if it's any 3rd party program and not the drivers.

I haven't tried those patches yet but I do have VirtualBox installed as I'm still undecided if I should give it a go yet...

Start -> Run, then paste this in.

%windir%\Windowsupdate.log

Find the entry for the failed update and there will be an error code. You can find it easy by doing a search for "Error". It will be in the format "Error #x########" for example "Error 0x80190194". Report back with the error code.

PTError: 0x80248014

This is the errorcode that is flooding the updatelog from 2007-09-09 till now. I never had problems updating, just updated indows Defender a minute ago, although the same error is recorded during the Defender update. (And of course also with the new performance updates for Vista)

PTError: 0x80248014

This is the errorcode that is flooding the updatelog from 2007-09-09 till now. I never had problems updating, just updated indows Defender a minute ago, although the same error is recorded during the Defender update. (And of course also with the new performance updates for Vista)

That is not a common error code, and from what I can find, there is no documentation from MS about it.

I'm guessing one of these:

1. Badly pirated copy of Vista (no offense, I'm not accusing you)

2. WGA validation got screwed up, you need to validate again

3. The Windows Update data store got corrupted

First, visit http://www.microsoft.com/genuine and click Validate Windows. Try the updates again.

If that doesn't work, then try this:

Open an elevated command prompt. (Go to Start -> Programs -> Accessories, right-click on Command Prompt, and choose "Run as administrator".)

In the command prompt window, run the following two commands:

net stop wuauserv

rmdir /s C:\Windows\SoftwareDistribution\DataStore

Don't close the command prompt window yet.

Rename the C:\Windows\WindowsUpdate.log file to some other name. (This isn't actually necessary, but will make it much easier to distinguish if WU is working properly after the fix)

Run the Registry Editor. (Go to Start -> Run, type "regedit" and press Enter.)

***Be careful, you can screw up your system if you make a mistake here***

In the Registry Editor tree, find HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate.

Right-click on WindowsUpdate in the tree and choose Delete.

Back in the command prompt window, run this command:

net start wuauserv

You can now close the command prompt window and the Registry Editor window.

Now run the Windows Update control panel. You'll be prompted to opt back into Microsoft Update and to reset your automatic-updates settings. The first "Checking for updates..." cycle will take longer than usual, since the data store needs to be rebuilt. Any previously-hidden updates (such as language packs) will be shown again and will need to be re-hidden.

If the problem was indeed a corrupted datastore, then you should find that

updates are now successfully detected. If not, then you should at least be no

worse off than you were.

I installed the 3 updates and things seemed to go well at first. Didn't really notice and speed difference or anything like that but I have now noticed I'm starting to have problems with Internet Explorer at times if it is trying to run a media player window or media type thing on a webpage. Example, going to MSN Videos or like a Myspace page with a video or music file on it. I am thinking that there was something with that update that was for Media player 11. Is there any way to install a update like that or is the only way to revert back is to do a system restore? At first I thought it had something to do with Adobe Flash because I thought it was crashing on those pages but I used tools from Adobe to uninstall everything Flash and reinstall it with no luck. I also reset Internet Explorers settings, from what I've heard it pretty much reverts it back to manufacturer's settings. Any ideas?

Windows Vista x64, Internet Explorer 7

That is not a common error code, and from what I can find, there is no documentation from MS about it.

I'm guessing one of these:

1. Badly pirated copy of Vista (no offense, I'm not accusing you)

2. WGA validation got screwed up, you need to validate again

3. The Windows Update data store got corrupted

First, visit http://www.microsoft.com/genuine and click Validate Windows. Try the updates again.

If that doesn't work, then try this:

Open an elevated command prompt. (Go to Start -> Programs -> Accessories, right-click on Command Prompt, and choose "Run as administrator".)

In the command prompt window, run the following two commands:

net stop wuauserv

rmdir /s C:\Windows\SoftwareDistribution\DataStore

Don't close the command prompt window yet.

Rename the C:\Windows\WindowsUpdate.log file to some other name. (This isn't actually necessary, but will make it much easier to distinguish if WU is working properly after the fix)

Run the Registry Editor. (Go to Start -> Run, type "regedit" and press Enter.)

***Be careful, you can screw up your system if you make a mistake here***

In the Registry Editor tree, find HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate.

Right-click on WindowsUpdate in the tree and choose Delete.

Back in the command prompt window, run this command:

net start wuauserv

You can now close the command prompt window and the Registry Editor window.

Now run the Windows Update control panel. You'll be prompted to opt back into Microsoft Update and to reset your automatic-updates settings. The first "Checking for updates..." cycle will take longer than usual, since the data store needs to be rebuilt. Any previously-hidden updates (such as language packs) will be shown again and will need to be re-hidden.

If the problem was indeed a corrupted datastore, then you should find that

updates are now successfully detected. If not, then you should at least be no

worse off than you were.

Thanks I tried that for my problem, and it didn't seem to work. (Legit Windows, just freshly formated)

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

    • No registered users viewing this page.
  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Here is one example of a tool that doesn't even need to be installed to be able to use: https://github.com/TheBobPony/MSEdgeTweaker Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!