Recommended Posts

that is wrong !

if you made a windows slipstream you SHOULD NOT use WU to upgrade to the latest build. WU itself even warns you about doing this.

Well then how should I do it? I grabbed it off the newsgroups.. the full install of 2162 and it comes up with a message still telling me I can't upgrade over the current version.

Well then how should I do it? I grabbed it off the newsgroups.. the full install of 2162 and it comes up with a message still telling me I can't upgrade over the current version.

Hi,

If you create a .txt file and paste in the following and rename it Install.XP.SP2.over.SP2.reg and double-click, it will delete 2 Registry values that should enable you to install 2169 over 2142.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]"CSDVersion"=-

"CSDBuildNumber"=-

BTW, it should be OK to do install 2169 over 2142 this way, but you take the risk, not me.

Cheerz

Install.XP.SP2.over.SP2.reg

If you create a .txt file and paste in the following and rename it Install.XP.SP2.over.SP2.reg and double-click, it will delete 2 Registry values that should enable you to install 2169 over 2142.

You could name it Turn.into.Longhorn.Server.1998.reg and it would do the same thing :rofl:

Filenames mean nothing people :yes:

You could name it Turn.into.Longhorn.Server.1998.reg and it would do the same thing :rofl:

Filenames mean nothing people :yes:

:whistle: :pinch: :rofl: :sleep: :rofl: :pinch: :whistle:

And your point is. :sleep:

I must say, that is a strange attitude for a Forum Moderator to have.

A question was asked and a solution posted, isn't that the point of these discussion forums. :sleep:

Cheerz :) ;) :)

And your point is. :sleep:

I must say, that is a strange attitude for a Forum Moderator to have.

A question was asked and a solution posted, isn't that the point of these discussion forums. :sleep:

Cheerz :) ;) :)

Just pointing it out ;)

Hi,

If you create a .txt file and paste in the following and rename it Install.XP.SP2.over.SP2.reg and double-click, it will delete 2 Registry values that should enable you to install 2169 over 2142.

BTW, it should be OK to do install 2169 over 2142 this way, but you take the risk, not me.

Cheerz

This is great... I followed the instructions stated and my update ran trouble free and the system now shows sp2162

Thanks mate :alien:

swlist.reg

Hi,

If you create a .txt file and paste in the following and rename it Install.XP.SP2.over.SP2.reg and double-click, it will delete 2 Registry values that should enable you to install 2169 over 2142.

BTW, it should be OK to do install 2169 over 2142 this way, but you take the risk, not me.

Cheerz

QUOTE

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]

"CSDVersion"=-

"CSDBuildNumber"=-

I merge this regfile, but i still can?t install. and i lost all my history updates on windows aupdate.

Is there an y undo file?

Anyone have any idea on how I can force 2162 to install over 2149, what I did was made a slipstreamed version of winxp with 2149. So I can't uninstall it!!. I really don't want to do a fresh install.. any help would be appreciated! Thanks..

y the hell do u want 2162?

just wait for the final it's only like 2 weeks away

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

    • No registered users viewing this page.
  • Posts

    • Google Chrome is killing all uBlock Origin bypasses, Microsoft Edge, Opera to follow by Sayan Sen For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions. Chromium contributor Andrey Bershanskiy shared details about recent Chromium changes and according to comments from Google engineer Devlin Cronin, Chrome has now started removing the flags that previously controlled MV2 availability. kExtensionManifestV2Disabled, the Chromium feature flag that allowed controlled disabling of MV2 add-ons, is now completely removed, which means you will likely no longer find uBlock Origin in your browser extensions list. He wrote: "The kExtensionManifestV2Disabled feature has been default-enabled for over a year. Remove the feature and the effectively-dead code. ... Any tests that relied on being in the "warning" phase (i.e., with the kExtensionManifestV2Disabled) for their sole behavior testing are removed, since this stage is no longer reachable." Cronin further explained why MV2 extensions are no longer allowed in supported Chrome versions as maintaining the associated functionality indefinitely is no longer possible. He cited growing technical difficulties and implementation complexities as well as security concerns. He wrote: "MV2 extensions are no longer allowed in any supported version of Chrome, and we are removing support for them and the associated functionality. We won't be able to provide / maintain this functionality indefinitely due to the complexity and tech debt, as well as the security risks it entails (we've actually found a number of bugs that are specific to MV2 lately). Of course, other browsers can continue supporting these if they so desire. Unfortunately, we won't be putting code behind a compilation flag ... We won't be removing all the MV2 code wholesale right away, so many of these things will continue working for awhile (but they will go away eventually, and some may go away sooner than others)." What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151. Here is a rundown of the changes coming in the final such releases of Chromium releases: Chromium 150 lost ExtensionManifestV2Disabled option Chromium 151 will loose ExtensionManifestV2Unsupported option Chromium 151 will loose ExtensionManifestV2Availability option Chromium 151 will likely loose AllowLegacyMV2Extensions option Other Chromium-based browsers like Opera and Microsoft Edge could soon follow suit too. Although it is not specified, Edge began disabling uBlock Origin back in February, and Opera could also stop the functioning of MV2 add-ons, even though it had committed to support MV2 for longer in October 2024. uBlock Origin developer Raymond Hill (gorhill) apparently stated the following: "For Opera I did submit 1.70.0 rather late, but this was weeks ago. A while ago I received an email from Opera that they plan to abandon MV2-based extension so maybe they are no longer allocating resources for reviewing such extensions." The email which developers like Gorhill mentions was received from Opera last year. Here is what it seemingly said: Hence for now the only Chromium browser that seems to be on-board fully with MV2 support is Brave, and perhaps Vivaldi as well. Meanwhile if you want to ditch Chromium browsers entirely then Mozilla Firefox is an excellent alternative as MV3 and MV2 are both supported. Of course the easiest solution is to switch to uBlock Origin Lite if you want to remain on Chrome, as it is MV3-based, but from our experience, uBO Lite does not seem to be as good as the original non-Lite version. Source: w3C (GitHub repo) As an online publication, Neowin too relies on ads for operating costs and, if you use an ad blocker, we'd appreciate being whitelisted. In addition, we have an ad-free subscription for $28 a year, which is another way to show support!
    • Write to your MP 😄 Like believing in Santa. Total surveillance IS the goal. Wake up.
    • This whole dumb age verification thing needs to die and be replaced by giving parents tools to control devices. Why am I required to plaster my ID all over the internet to prove I'm old enough when parents should be the ones dictating what their kids are doing on their phones. Apple released great set of tools for iPhones coming to iOS 27 that do just that. Why are governments not mandating that kind of control to phone makers to built them into phones. This whole thing is so absolutely idiotic it's wild.
    • Remeber this decade, when the free internet died... tell your grand kids about this, record there reaction and post it on InstaTwitBook.com
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!