Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

[WIP] Windows Vista Extended Kernel


win32
 Share

Recommended Posts

10 hours ago, Vistapocalypse said:

Installation is possible, but I would advise against it because you will get missing dependency errors with .NET software that should work on vanilla Vista (see this May 17, 2019 post). Unless you simply must test some program that specifically requires 4.8, you would get better results with any lower 4.x version.

I'm trying to run Bloons TD 6 Steam version. What is weird is that the game worked in the past with the Kernel and without .net framework 4.8 (it would prompt me to install it, but I could still run it), but now doesn't. I uninstalled it and tried to reinstall it, but it throws an error. I should note that the game and steam are in my osver.ini file (otherwise it will tell me there is no connection). I should note that Bloons TD 5, also from Steam works, but this game was released when Steam still supported Vista.

  • Upvote 1
Link to comment
Share on other sites


4 hours ago, Jakob99 said:

I'm trying to run Bloons TD 6 Steam version. What is weird is that the game worked in the past with the Kernel and without .net framework 4.8 (it would prompt me to install it, but I could still run it), but now doesn't. I uninstalled it and tried to reinstall it, but it throws an error. I should note that the game and steam are in my osver.ini file (otherwise it will tell me there is no connection). I should note that Bloons TD 5, also from Steam works, but this game was released when Steam still supported Vista.

I used to have .net framework 4.7.2 installed on Vista. Some programs displayed an error "A programs has stopped working", but I could minimize it (not close) and the application worked fine (for example BlueStacks3), others like Visual Studio 2010 Express didn't run at all. Currently I use 4.6.1 (officially supported on Server 2008), but 4.6.2 is stable too. Most modern programs still support those versions.

  • Like 1
Link to comment
Share on other sites

I tried to run Windows 8 task manager (much better that Vista/7 one) on Windows Vista with extended kernel and got this error:

taskmgrerror.JPG.52fc0e3431b7856b9a73844474c192f9.JPG

Translation: Cannot launch the application, because it's simultaneous configuration is invalid. More details can be found in the application's event log.

Event log screenshot:

eventlog.PNG.d73b146d1f8af4f958d1117ecd32d2eb.PNG

Translation: Cannot generate the activation context for [path]. The setting http://schemas.microsoft.com/SMI/2005/WindowsSettings^autoElevate is not registered.

Does anyone know how to "register" this thing? (I have no idea what "simultaneous configuration" or "activation context" are :))

EDIT:

At first I thought that "WindowsSettings" is somehow UWP related, but it looks like it's not, because the website above was created in 2009 http://web.archive.org/web/20090625053858/http://schemas.microsoft.com/SMI/2005/WindowsSettings^autoElevate. It has been broken for 12 years now:thumbdown.

 

Edited by TSNH
Link to comment
Share on other sites

15 hours ago, TSNH said:

Currently I use 4.6.1 (officially supported on Server 2008), but 4.6.2 is stable too. Most modern programs still support those versions.

I was almost certain that .NET 4.6.0 was the last to officially support Server 2008 SP2, but I just looked it up and and a Microsoft document now shows 4.6.2 as supported!? (But it neglects to mention 4.6.1 in connection with 2008 SP2, so quite possibly an error. This is near the bottom of https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements .) Special procedures are were required to install 4.6.2 or above on Vista. Edit: Subsequent posts reveal that installing 4.6.2 is no longer a problem, assuming that SHA-2 support has been installed. Btw updates for 4.6.1 and earlier are supposed to end on April 26.

Edited by Vistapocalypse
You live and learn.
  • Like 1
  • Upvote 2
Link to comment
Share on other sites

1 hour ago, TSNH said:

I tried to run Windows 8 task manager (much better that Vista/7 one) on Windows Vista with extended kernel and got this error:

taskmgrerror.JPG.52fc0e3431b7856b9a73844474c192f9.JPG

 

I solved it by following this guide: https://www.reddit.com/r/techsupport/comments/6gajcs/fix_for_activation_context_generation_failed_the/

Here is my exported registry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\amd64_microsoft-windows-settings_31bf3856ad364e35_none_5e7b0013834d1c8b\6.0.6000.16386\Settings]
"disableTheming"="xsd:string"
"dpiAware"="xsd:string"
"autoElevate"="xsd:string"

Note that numbers in the path might be different for you.

Many dependences are still missing:

user32.dll: CreateWindowInBand, GetCurrentImputMessageSource, GetWindowBand

and there are tons of missing API-MS-WIN-CORE files:

obraz.thumb.png.6a6c92c1aa76fe8bd663c6690dd473c4.png

Edited by TSNH
Link to comment
Share on other sites

1 hour ago, Vistapocalypse said:

.NET 4.6.0 was the last to officially support Server 2008 SP2, but I just looked it up
and a Microsoft document now shows 4.6.2 as supported!?
(removed for brevity)
Special procedures are required to install 4.6.2 or above on Vista.

I was intrigued by your report :P, so I connected an external HDD in which I had archived a copy of
NDP462-KB3151800-x86-x64-AllOS-ENU.exe
originally downloaded Sep 14th 2016; that off-line installer was dual-signed (SHA1+SHA2) on July 15th 2016;
running that installer now, after file extraction, generates the familiar error below:

7nMr5yc.jpg

I closed that installation attempt and then went to
https://dotnet.microsoft.com/download/dotnet-framework/thank-you/net462-offline-installer
Direct link is 

https://go.microsoft.com/fwlink/?linkid=2099468

The latter fetched file
ndp462-kb3151800-x86-x64-allos-enu.exe
(in small letters this time ;)) which is only SHA-2 signed on May 1st 2021;
my Vista SP2 32-bit system has SHA-2 support installed, so when I ran that second off-line installer, and after file extraction (takes a few seconds, because it scans ALL your drives to choose the one with maximum FREE disk space), I was, surprisingly, presented with:

MRBYjlg.jpg

Now, I didn't click Install to go on with the 4.6.2 installation, because I wasn't yet ready to part with my existing, perfectly working, 4.6.1 setup... Perhaps the 4.6.2 installation would have aborted at a later stage, or perhaps NOT... :dubbio:The thing is the updated .NF462 setup doesn't immediately barf when it detects NT6.0; another kind soul with Vista SP2 in a VM could try that new installer to explore whether it "requires special procedures" to complete the installation... 

FWIW, since this revised setup targets WS2008SP2, I expect it would require a special minimum set of WS2008SP2 updates to be present in your Vista SP2 image... :whistle:

  • Like 2
  • Upvote 1
Link to comment
Share on other sites

1 hour ago, VistaLover said:

I was intrigued by your report :P, so I connected an external HDD in which I had archived a copy of
NDP462-KB3151800-x86-x64-AllOS-ENU.exe
originally downloaded Sep 14th 2016; that off-line installer was dual-signed (SHA1+SHA2) on July 15th 2016;
running that installer now, after file extraction, generates the familiar error below:

7nMr5yc.jpg

I closed that installation attempt and then went to
https://dotnet.microsoft.com/download/dotnet-framework/thank-you/net462-offline-installer
Direct link is 

https://go.microsoft.com/fwlink/?linkid=2099468

The latter fetched file
ndp462-kb3151800-x86-x64-allos-enu.exe
(in small letters this time ;)) which is only SHA-2 signed on May 1st 2021;
my Vista SP2 32-bit system has SHA-2 support installed, so when I ran that second off-line installer, and after file extraction (takes a few seconds, because it scans ALL your drives to choose the one with maximum FREE disk space), I was, surprisingly, presented with:

MRBYjlg.jpg

Now, I didn't click Install to go on with the 4.6.2 installation, because I wasn't yet ready to part with my existing, perfectly working, 4.6.1 setup... Perhaps the 4.6.2 installation would have aborted at a later stage, or perhaps NOT... :dubbio:The thing is the updated .NF462 setup doesn't immediately barf when it detects NT6.0; another kind soul with Vista SP2 in a VM could try that new installer to explore whether it "requires special procedures" to complete the installation... 

FWIW, since this revised setup targets WS2008SP2, I expect it would require a special minimum set of WS2008SP2 updates to be present in your Vista SP2 image... :whistle:

I can confirm everything that you are saying. First I tried with my old .NET 4.6.2 offline setup that was signed on 15.07.2016 with both SHA-1 and 256 and I got the "unsupported OS" error. Than i downloaded a new installer from Microsoft, and it worked!

obraz.png.d861f2eb9a89316f9c30961c5ca317bf.pnginstalling.PNG.ecf366de21e507d401ef80e2bae8c3a3.PNGfinish.PNG.4f5a541bcb4e0cbce0a7c887fc742254.PNG

I'm going to try 4.7.2 next:)

 

  • Like 1
Link to comment
Share on other sites

2 hours ago, VistaLover said:

Now, I didn't click Install to go on with the 4.6.2 installation, because I wasn't yet ready to part with my existing, perfectly working, 4.6.1 setup... Perhaps the 4.6.2 installation would have aborted at a later stage, or perhaps NOT... :dubbio:The thing is the updated .NF462 setup doesn't immediately barf when it detects NT6.0; another kind soul with Vista SP2 in a VM could try that new installer to explore whether it "requires special procedures" to complete the installation... 

It does install successfully

pro.png.3ebbefac80af18f5038c4592be1baabb.png

I have the latest ex. kernel installed on the machine and all the updates that are required

However I don't have any apps installed that use it so you can suggest some

4 hours ago, Vistapocalypse said:

I was almost certain that .NET 4.6.0 was the last to officially support Server 2008 SP2, but I just looked it up and and a Microsoft document now shows 4.6.2 as supported!? (But it neglects to mention 4.6.1 in connection with 2008 SP2, so quite possibly an error. This is near the bottom of https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements .) Special procedures are required to install 4.6.2 or above on Vista.

Check the bottom of this page https://support.microsoft.com/en-us/topic/the-net-framework-4-6-2-offline-installer-for-windows-9dce3874-a9e5-9b11-289d-5594824aafe0

I thought the last version for server 2008 sp2 was 4.6.1

  • Like 2
  • Upvote 1
Link to comment
Share on other sites

6 minutes ago, TSNH said:

I'm going to try 4.7.2 next:)

It didn't work with 4.7.2 so I think Microsoft changed the system requirements on purpose.

Updates that i had installed: all Vista updates till 2017 + KB4019478 - D3Dcompiler-x64 + SHA-2 updates KB4039648-v2,KB4493730, KB4474419 + Extended Kernel

The "4.6.2" text next to "Server 2008 SP2" was added quite recently:

http://web.archive.org/web/20210506200116/https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements

http://web.archive.org/web/20211006034517/https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements

 

Edited by TSNH
  • Like 2
Link to comment
Share on other sites

1 hour ago, winvispixp said:

I don't have any apps installed that use it so you can suggest some

https://github.com/ShareX/ShareX/releases/tag/v13.0.1

default ShareX.exe.config file:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6.2" />
  </startup>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <probing privatePath="Languages" />
    </assemblyBinding>
    <AppContextSwitchOverrides value="Switch.UseLegacyAccessibilityFeatures=false;Switch.UseLegacyAccessibilityFeatures.2=false" />
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-12.0.0.0" newVersion="12.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
  <uri>
    <idn enabled="All" />
    <iriParsing enabled="true" />
  </uri>
  <appSettings>
    <add key="EnableWindowsFormsHighDpiAutoResizing" value="true" />
  </appSettings>
</configuration>

:)

Link to comment
Share on other sites

3 hours ago, TSNH said:

Microsoft must have decided that ESU customers running 2008 SP2 deserve to have a supported .NET version after April 26, 2022. :) (Looks like I was formerly correct that 4.6.0 was the last officially supported version.) Thanks to all who have investigated this interesting development! :thumbup

  • Like 1
  • Upvote 1
Link to comment
Share on other sites

5 hours ago, TSNH said:

I can confirm everything that you are saying.
(snipped)
i downloaded a new installer from Microsoft, and it worked!

5 hours ago, winvispixp said:

It does install successfully

Thank you both for testing and confirming :) :thumbup

5 hours ago, TSNH said:

... Consistent with the digital SHA-2 signature date (2021-05-01) of the revised 4.6.2 setup; the page must've been edited soon after May 6th... ;)

10 hours ago, Vistapocalypse said:

(But it neglects to mention 4.6.1 in connection with 2008 SP2, so quite possibly an error.

1 hour ago, Vistapocalypse said:

Microsoft must have decided that ESU customers running 2008 SP2 deserve to have a supported .NET version after April 26, 2022. :) (Looks like I was formerly correct that 4.6.0 was the last officially supported version.)

Bingo! :thumbup It's all clear now...
The ESU plan for WS2008SP2 ends in Jan 2023, however security updates support for officially sanctioned .NET FW 4.6 will end, as said, in late Apr 2022; that would've created a period of ca. 9 months, during which installed 4.6 would have stayed unpatched... :(
Possibly due to technical reasons, M$ deemed it easier to patch 4.6.2 (still supported past Apr 2022) to also install under WS2008SP2, rather than modify and offer 4.7.x (or higher) to existing WS2008SP2 ESU customers...
And the omission of 4.6.1 from the linked article isn't an error; we already know that 4.6.1 installs successfully under NT 6.0, but it was never officially supported (as in via MU) there :no: ; M$'s plan is to migrate WS2008SP2 ESU paying customers from 4.6 directly to 4.6.2 before/soon after Apr 2022 (till Jan 2023, when ESU ends); since 4.6.1 EOLs at the same time as 4.6, no reason for M$ to even mention it in that scenario...

But another thing bugs me now: How is the revised (2021) 4.6.2 setup different internally to the first (2016) release? Does it embed ALL security updates issued for 4.6.2 from Jul 2016 to May 2021? File sizes are almost identical, so this fact isn't revealing anything :( ... Of course, MU would never work for 4.6.2 under Vista SP2, still, one has to know what updates to download manually from MUC; and then there's the "problem"/grey area of installing from local files ESU .NET FW 4.6.x updates...

In any case, I understand this is the Windows Vista Extended Kernel thread, so I'm party responsible for (slightly?) derailing it :blushing: ; however, this is info important to the broader Vista Community, so if the mods decide it should be better placed elsewhere (info = series of recent posts about .NET FW 4.6.2/Vista | WS2008), feel free to do so... :)

Edited by VistaLover
  • Like 1
  • Upvote 1
Link to comment
Share on other sites

On 11/1/2021 at 12:03 AM, Vistapocalypse said:

The extended kernel does not require KB4493471 that you say caused a BSOD that once affected many Avast/AVG users, however it does require KB4474419.

Says who ? Did you try to do it yourself ? I tried , it works , because all needed files are already inside , ask win32 to open it and check. I shall tell you more , I tried to install Nvidia HD driver from 2021 and Vista said it is not signed , but right after I installed the aforementioned update , it let me proceed with the installation ! So it includes SHA2 too ?! (I'm not sure , I'm just guessing here). So don't go attacking me again , please . I only write about my personal experiences , and I don't understand why some new member is allowed to post whatever he wants and you don't have anything against  it , but with me you call it "fake news" ? Also , I'm sorry, I forgot to incude quotes in some previous post , will you forgive me please , OK ? 

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...