[WIP] Windows Vista Extended Kernel

[Bizzbob]

Sorry to hear about the problems you're having Scarf. I can't say I know of any way my batch script could interfere with Win32's installer, so unfortunately I'm probably not going to be of much use here. Are you experiencing a crash with my script before it gets to the option to reboot?

As for any 'remnants' from running my script, there shouldn't really be much. The script copies Win32's files to a temp folder under 'C:\extendedkernel_*randomnumbers*' and writes these temp files into the registry entry located at 'HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations', so that Windows would move and rename them on reboot. The folder is normally deleted at reboot. You can try and have a look in these places to see if there are any temp folders or registry entries to delete in the event of a failed install, although PendingFileRenameOperations is normally cleared by Windows on reboot anyway, and I'm not convinced this is the reason for the errors you are seeing.

Note that if the temporary folder under C:\ needs deleting, you will need to take ownership and give yourself permissions to the folder's contents first, as the custom install script makes TrustedInstaller the owner of the files.

[Scarf32]

7 hours ago, Dixel said:

I see, I have a question, what made you use non-win32 installer in the first place? And what does Bizzbob have to say? Perhaps ask him in his topic then?

Aand If I were you, I'd try a clean install of Vista + the installer by win32. It worked fine for me, always!

MAYBE BECAUSE WIN32'S INSTALLER NEVER WORKED ON MY PC??? And also it is a hassle to change everything manually and bizzbob's installer is the best so if you stop complaining about me using a better installer and not wasting my time i will appreciate it

Edited July 1, 2023 by Scarf32

[Scarf32]

4 hours ago, Bizzbob said:

Sorry to hear about the problems you're having Scarf. I can't say I know of any way my batch script could interfere with Win32's installer, so unfortunately I'm probably not going to be of much use here. Are you experiencing a crash with my script before it gets to the option to reboot?

As for any 'remnants' from running my script, there shouldn't really be much. The script copies Win32's files to a temp folder under 'C:\extendedkernel_*randomnumbers*' and writes these temp files into the registry entry located at 'HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations', so that Windows would move and rename them on reboot. The folder is normally deleted at reboot. You can try and have a look in these places to see if there are any temp folders or registry entries to delete in the event of a failed install, although PendingFileRenameOperations is normally cleared by Windows on reboot anyway, and I'm not convinced this is the reason for the errors you are seeing.

Note that if the temporary folder under C:\ needs deleting, you will need to take ownership and give yourself permissions to the folder's contents first, as the custom install script makes TrustedInstaller the owner of the files.

Yes, the exact point where it crashes is: "Updating registry and marking system files to replace"

[winvispixp]

1 hour ago, Scarf32 said:

wasting my time

you would have had a fully working pc by now if you thought about backing up your files and just reinstalling windows. it's clear it's a windows issue that none of us experienced until now and we don't have a better option at the moment
you said it crashes while trying to make a backup or restore point. are you sure you haven't disabled some windows services that are necessary? perhaps one of the programs you already installed messed you up, who knows?

[Scarf32]

1 hour ago, winvispixp said:

you would have had a fully working pc by now if you thought about backing up your files and just reinstalling windows. it's clear it's a windows issue that none of us experienced until now and we don't have a better option at the moment
you said it crashes while trying to make a backup or restore point. are you sure you haven't disabled some windows services that are necessary? perhaps one of the programs you already installed messed you up, who knows?

Yes but what i was saying is that this guy thinks it's my fault that windows is broken because i used bizzbob installer wich is not so with "stop wasting my time" i meant stop telling me this. Also can you make me a list of necessary updates to install in order to install ext kernel. So i can reinstall vista

[winvispixp]

3 hours ago, Scarf32 said:

Also can you make me a list of necessary updates to install in order to install ext kernel. So i can reinstall vista

i don't know which are required and which are not, i just got all of them
but @D.Draker might be able to answer your question

[mina7601]

24 minutes ago, winvispixp said:

i don't know which are required and which are not, i just got all of them
but @D.Draker might be able to answer your question

Basically, when wanting to install the updates required for extended kernel, I just follow TSNH's guide (the "Preparations:" section, from 3. to 6.). Works everytime.

Edited July 1, 2023 by mina7601

[Scarf32]

21 minutes ago, mina7601 said:

Basically, when wanting to install the updates required for extended kernel, I just follow TSNH's guide (the "Preparations:" section, from 3. to 6.). Works everytime.

Ok thanks, i will update everyone when i'm done doing everything

[LiptonAcer]

On 7/1/2023 at 2:34 AM, yotoprules said:

Is anyone else having the problem where all the permissions get screwed up? I am unable to run anything as admin and several features are broken.
Only way to fix it is to boot into safe mode and run SFC /scannow which puts my OS back into a usable state.
I am using a fully updated Windows Vista SP2 X64.

After hard work testing all updates on Windows Vista; I finally managed to make the Extended Kernel of March 2023 revision 1 work with the Windows Vista esu! Several updates are problematic: KB5003210, KB4580385 are most responsible as well as superseded 2022 updates. Cumulative updates are also to be banned. The solution is: to remove all the 2022 updates that have been installed on the system and to install only the non-superseded updates which are security only, and to remove the two updates KB5003210, KB4580385 Then, we can install the extended kernel without having any problem!

Updates 2022 need to remove : kb5009601-kb5010403-kb5011486-kb5011525-kb5011942-kb5012137-kb5012150-kb5012632-kb5012658-kb5013619-kb5013636-kb5014006-kb5014010-kb5014743-kb5014752-kb5015866-kb5015870-kb5016129-kb5016669-kb5016686-kb5017358-kb5017371-kb5018413-kb5018446-kb5018450-kb5020005-kb5020019-KB5021289-KB5021293-KB5021657

Updates 2022 need to install : kb5009601-kb5010403-kb5011525-kb5012150-kb5012632-kb5013619-kb5014006-kb5014743-kb5015870-kb5016129-kb5016686-kb5017371-kb5018446-kb5020005-kb5020895-kb5021293

I had the same problem as you and when I deleted the maj to replace them with the others it solved the problem. I made a video of my problem. https://www.youtube.com/watch?v=BmPZTJX18sE

[Scarf32]

On 7/2/2023 at 8:55 AM, LiptonAcer said:

After hard work testing all updates on Windows Vista; I finally managed to make the Extended Kernel of March 2023 revision 1 work with the Windows Vista esu! Several updates are problematic: KB5003210, KB4580385 are most responsible as well as superseded 2022 updates. Cumulative updates are also to be banned. The solution is: to remove all the 2022 updates that have been installed on the system and to install only the non-superseded updates which are security only, and to remove the two updates KB5003210, KB4580385 Then, we can install the extended kernel without having any problem!

Updates 2022 need to remove : kb5009601-kb5010403-kb5011486-kb5011525-kb5011942-kb5012137-kb5012150-kb5012632-kb5012658-kb5013619-kb5013636-kb5014006-kb5014010-kb5014743-kb5014752-kb5015866-kb5015870-kb5016129-kb5016669-kb5016686-kb5017358-kb5017371-kb5018413-kb5018446-kb5018450-kb5020005-kb5020019-KB5021289-KB5021293-KB5021657

Updates 2022 need to install : kb5009601-kb5010403-kb5011525-kb5012150-kb5012632-kb5013619-kb5014006-kb5014743-kb5015870-kb5016129-kb5016686-kb5017371-kb5018446-kb5020005-kb5020895-kb5021293

I had the same problem as you and when I deleted the maj to replace them with the others it solved the problem. I made a video of my problem. https://www.youtube.com/watch?v=BmPZTJX18sE

I know you can't put links but can you tell me a site to download vista iso? Because i don't know wich to trust. Is archive org safe?

Edited July 3, 2023 by Scarf32

[Sergiaws]

yea, archive.org might be the best source for older operating systems.

[Scarf32]

1 hour ago, Sergiaws said:

yea, archive.org might be the best source for older operating systems.

Ok thanks

[LiptonAcer]

2 hours ago, Scarf32 said:

I know you can't put links but can you tell me a site to download vista iso? Because i don't know wich to trust. Is archive org safe?

To install Windows Vista I prefer to start from an iso of Windows Vista RTM and to configure it correctly and to install the updates one by one, its stability improves enormously than to start on an iso of sp2 already made.

[Scarf32]

4 hours ago, LiptonAcer said:

To install Windows Vista I prefer to start from an iso of Windows Vista RTM and to configure it correctly and to install the updates one by one, its stability improves enormously than to start on an iso of sp2 already made.

Is it that much of an improvement? Because losing 3 hours installing every single update for me it's not worth it

[Cocodile]

I use a legit non-modified Vista x64 SP2, then install everything according to win32's instructions, no need to get as low as RTM! I never used a third party installer, can't say anything about it!