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

    • If you actually used it instead of responding like a petulant child you might be surprised. I switched from Google some time ago and have been very satisfied.
    • I am one of the first people to use the DXVK technology. In the channel below you can see some videos that I have made using this technology, including Assassin's Creed Odyssey. https://www.youtube.com/@nahum7995/videos Assassin's Creed Odyssey experienced several bugs and technical issues during its first months after release. It launched with its own fair share of funny but frustrating glitches. I ran it on DXVK 9 days after its release and I played it for many hours but didn't see a single significant bug on Linux. Assassin's Creed Odyssey is widely celebrated for pushing the franchise in bold new directions and specifically for nailing several elements better than any other title in the AC series: Player Choice & Branching Narrative, The Mercenary & Cultist System, Mythological Integration, Overpowered Combat Abilities, Open World Exploration But what I'm trying to point out is that this game wasn't quite playable on most windows systems, until a few months after its release when most of the bugs were fixed. However, on Linux it ran completely flawless from day one, although DXVK had seen little development and refinement at the time. What do you think the situation will be in 2026 now that most bugs and glitches of DXVK have been completely eliminated? This is information from Google about these situations that I am quoting. In many cases, using DXVK (a translation layer that converts DirectX 9, 10, or 11 into Vulkan) can result in more stable frame times and higher performance than native Windows rendering. This happens primarily by bypassing driver overhead and multithreading draw calls that were previously restricted to a single CPU core. Older APIs (like DirectX 9 and 11) are largely single-threaded on the CPU side. DXVK translates these calls to Vulkan, which is highly multi-threaded. This reduces CPU-bound stuttering on weaker processors. In certain cases, GPU manufacturers (especially AMD) have significantly better and more modern Vulkan drivers than they do for legacy DirectX. Vulkan gives developers—and in this case, the translation layer—closer control over how resources are held in VRAM. This can prevent micro-stutters and sudden frame drops during chaotic gameplay. Yes, certain games, particularly older DirectX 9 to 11 titles, can run with fewer crashes on DXVK than on native Windows. By intercepting DirectX draw calls and translating them into the modern, highly efficient Vulkan API, DXVK bypasses the limitations and poor driver support that cause instability in aging game engines. PlayStation 1, PlayStation 2 and PlayStation 3 can be easily and perfectly emulated on Linux. In fact, modern Linux emulators offer high-performance upscaling, widescreen patches, and automatic controller mapping out of the box.                                                                                                                                                                                                                                                                                                                                 PlayStation 1/2/3 games look drastically better on Linux thanks to resolution upscaling. Furthermore, it is also a fact that you cannot play many fun games on Windows either, isn't it? - The Nintendo Switch has an extensive library of exclusive games. - PlayStation has an extensive library of exclusive games - Android has "mobile-exclusive" games, meaning they are exclusive to mobile devices (iOS and Android) and aren't available on PC or consoles. And finally, it is also the case that in the next five years there will be games that millions of people will say you absolutely must play and that they want to play this specific game that released a few days ago. However, the other side of this story is that currently, absolutely no one cares that they cannot play these upcoming games right now.
    • Flameshot 14.0 RC3 by Razvan Serea Flameshot is a free and open-source, cross-platform tool to take screenshots with many built-in features to save you time. Using Flameshot is as simple as launching, dragging the selection box to cover the area you want to capture, making annotations as needed in on-screen and saving the shot to your computer, all with a very simple and straightforward interface. Flameshot allows users to simply upload their screenshots directly to the cloud in order to easily share it with others. You can upload your image directly to Imgur with a single click and share the URL with others. In-app screenshot editing - You can choose to add an arrow mark, highlight text, blur a section (blur or pixelate an area), add a text, draw something, add a rectangular/circular shaped border, add an incrementing counter number, and add a solid color box with Flameshot's built-in editing tools. Command-line interface (CLI) - Flameshot has several commands you can use in the terminal without launching the GUI via a command line interface. The command line interface lets you script Flameshot and use it as the subject of key binds. Flameshot 14.0 RC3 changelog: Translations update from Hosted Weblate by @weblate in #4612 Translations update from Hosted Weblate by @weblate in #4619 Fix pin position on Windows for scaled screen by @ElTh0r0 in #4614 Cmake Analyzers by @ElTh0r0 in #4613 Translations update from Hosted Weblate by @weblate in #4632 fix(macos): prevent config tab content from rendering behind tab bar by @Mitnitsky in #4627 fix(macos): use CGRequestScreenCaptureAccess instead of grabWindow for permission request by @Mitnitsky in #4617 Fix KDE Plasma keyboard shortcut config file by @ElTh0r0 in #4637 fix(macos): fix clipboard copy failing from tray and GUI by @Mitnitsky in #4629 feature(macos): show dock icon when config window is open by @Mitnitsky in #4628 Option to disable tray icon on Windows by @ElTh0r0 in #4634 Translations update from Hosted Weblate by @weblate in #4642 fix(macos): make fullscreen capture overlay configurable by @Mitnitsky in #4622 Update GH actions using Node.js 24 by @ElTh0r0 in #4660 fix issue with screen selection in non interactive mode by @borgmanJeremy in #4667 Uniformize both spec files + ninja build openSUSE by @QuentiumYT in #4658 screengrabber: pass non-empty parent_window to xdg-desktop-portal by @artefaktor93 in #4664 Allow multiple flameshot GUI instances (fix for #3177) by @ElTh0r0 in #4680 Unify Linux ARM CI into Linux CI (also drop QEMU) by @theofficialgman in #4702 respect system proxy settings by @borgmanJeremy in #4674 Replace ifdef LINUX with UNIX to include BSD systems by @ElTh0r0 in #4700 Download: Flameshot 14.0 RC3 | 18.1 MB (Open Source) Download: Flameshot Portable | 53.0 MB Links: Flameshot Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • I found that stability back then was really down to the motherboard manufacturer. Back then i stuck with Microstar motherboards and VIA chipsets as they were ultra reliable. Most stuff was done with jumpers and left little room for user created problems 👍
  • Recent Achievements

    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
  • Popular Contributors

    1. 1
      +primortal
      490
    2. 2
      PsYcHoKiLLa
      232
    3. 3
      Skyfrog
      78
    4. 4
      FloatingFatMan
      68
    5. 5
      Michael Scrip
      58
  • Tell a friend

    Love Neowin? Tell a friend!