TSNH

If so an FTP server on a local network will probably be the easiest transfer method. As a server you can use an old phone or ISS on a Windows virtual machine (even NT4 server would work)

Does it show up at all in My Computer when you connect it and allow photo transfer on the phone's screen or this error pops up when you initiate the transfer? I was able to test on an older iPhone (not 15pro) but updated to IOS 18 and Windows Vista and photo transfer worked there without any iTunes.

As a bonus here are Vista-compatible .reg files that add PowerShell 7 to the context menus To use them copy, save a .reg and apply Open PowerShell here: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\Directory\Background\shell\openpwsh] "MUIVerb"="&Open PowerShell" "Icon"="C:\\Program Files\\PowerShell\\7\\pwsh.exe" [HKEY_CLASSES_ROOT\Directory\Background\shell\openpwsh\command] @="cmd.exe /k pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\"" Open a folder in PowerShell: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\Directory\shell\PowerShell7x64] "MUIVerb"="&Open in PowerShell" "Icon"="C:\\Program Files\\PowerShell\\7\\pwsh.exe" [HKEY_CLASSES_ROOT\Directory\shell\PowerShell7x64\command] @="cmd.exe /k pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\" || pwsh.exe -NoExit -RemoveWorkingDirectoryTrailingCharacter -WorkingDirectory \"%V!\" -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'\"" Run .ps1 file in PowerShell: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\Microsoft.PowerShellScript.1\Shell\PowerShell7x64] "Icon"="C:\\Program Files\\PowerShell\\7\\pwsh.exe" "MUIVerb"="Run with PowerShell 7" [HKEY_CLASSES_ROOT\Microsoft.PowerShellScript.1\Shell\PowerShell7x64\Command] @="cmd /k pwsh.exe -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'; if((Get-ExecutionPolicy ) -ne 'AllSigned') { Set-ExecutionPolicy -Scope Process Bypass }; & '%1'\" || pwsh.exe -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'; if((Get-ExecutionPolicy ) -ne 'AllSigned') { Set-ExecutionPolicy -Scope Process Bypass }; & '%1'\" || pwsh.exe -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'; if((Get-ExecutionPolicy ) -ne 'AllSigned') { Set-ExecutionPolicy -Scope Process Bypass }; & '%1'\" || pwsh.exe -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'; if((Get-ExecutionPolicy ) -ne 'AllSigned') { Set-ExecutionPolicy -Scope Process Bypass }; & '%1'\" || pwsh.exe -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'; if((Get-ExecutionPolicy ) -ne 'AllSigned') { Set-ExecutionPolicy -Scope Process Bypass }; & '%1'\" || pwsh.exe -Command \"$host.UI.RawUI.WindowTitle = 'PowerShell 7 (x64)'; if((Get-ExecutionPolicy ) -ne 'AllSigned') { Set-ExecutionPolicy -Scope Process Bypass }; & '%1'\"" As you can see they try to retry the PowerShell launch if it fails to overcome 7.2.2's bug, and are also in a bit different format than those supplied with PowerShell installer because those didn't work with Vista. I still haven't figured out how to make run as administrator versions

PowerShell 7 on Windows Vista Extended Kernel done properly So here's how to install 64-bit PowerShell 7 on Windows Vista with Extended Kernel. You MUST use EXACLY version 7.2.2. If you want to know why is that, go to the section why 7.2.2?, but for now here's a Quick step-by-step guide: 1. Install Windows Vista Extended Kernel October 2022 x64 version if you haven't already (only x64 files are needed, less stable x86 ones not required) https://msfn.org/board/topic/183046-guide-vista-extended-kernel-installation/ 2. Download zipped version of PowerShell 7.2.2 (PowerShell-7.2.2-win-x64.zip) from GitHub https://github.com/PowerShell/PowerShell/releases/tag/v7.2.2 3. Extract it somewhere, from now on this somewhere is assumed to be "C:\Program Files\PowerShell\7\" so that the path to the main executable is "C:\Program Files\PowerShell\7\pwsh.exe" 4. Add this to your osver.ini in C:\Windows (if it's not there create it) [C:\Program Files\PowerShell\7\pwsh.exe] Enabled=1 MinorVersion=1 5. Add "C:\Program Files\PowerShell\7" without quotes to your system Path. To do that go to ControlPanel -> System and Maintenance -> System -> System Properties -> Advanced (it's a tab) -> Environmental Variables. Look for the Path variable and add the aforementioned path to other things after a semicolon ( ; ), thats how things are separated there. 6. Download and unzip this special shortcut https://forum.legacydev.org/viewtopic.php?f=27&t=231 and put it in "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell" so that it appears in the start menu next to the old-school WindowsPowerShell. You can also put it in "%appdata%\Microsoft\Internet Explorer\Quick Launch" to add it to quick launch. The 2 things that are special about the shortcut I've made are: It launches cmd to launch PowerShell, which is a workaround to a problem with 7.2.2 more in why 7.2.2? It behaves like a WindowsPowerShell window, so it has a range select feature and the iconic PowerShell blue color. 7. Enjoy Why 7.2.2? So you could just install 7.2.17, 7.2.24 or any other newer 7.2.x version, and it would work fine... mostly But sometimes those versions hang on startup and never launch staying in a non-functional state which even takes a few seconds when you decide close it. On some machines like 9/10 launch tries are successful on some almost none. There are even reports of this occurring on Windows 10: https://old.reddit.com/r/PowerShell/comments/v6arrr/powershell_72x_almost_always_hangs_when_launched/?rdt=40615 https://github.com/PowerShell/PowerShell/issues/17558 But I've managed to reproduce this issue only on Windows Vista machines and multiple ones. 7.2.3 and newer as well as newer 7.1.x like 7.1.7 are affected by this issue on Vista 7.2.1 and older as well as older 7.1 and 7.0 on the other hand just fail to launch at all showing a Failed to initialize properly ... smth error. So if it wasn't for 7.2.2 you would have to go back to PowerShell 6 to get a working version But 7.2.2 has it's own issue where it sometimes immediately closes after launching an exe. Fortunately it doesn't do this when launched from another command line tool, that's why it was necessary to make a shortcut that launches cmd first and pwsh next

Is Nvidia container service running? Unfortunately I had to enable it, otherwise the settings would reset (Windows 8.0 here)

What are the improvements in this version vs Windows 7 paint?

iOS is a heavily locked platform, in US it only allows app installation through the ofiicial AppStrore, while Android users can probably just sideload an apk and use a VPN to access Tiktok

iPhone users will finally feel the need for sideloading.

Where did you find this info? Compressing audio in a lossless way should be theoretically possible and that's exactly what FLAC is supposed to accomplish. It would have no reason to exist otherwise.

Correct me if I'm wrong, but this autorun thing makes me think that you are launching the setup from another running Windows installation. So try booting from the setup disc instead.

Thanks! That's amazing, tested and working Would it be possible to use Windows Vista's explorer instead of Windows 7 one? EDIT: Got a helpful reply on discord about this. Follow this manual installation guide, https://github.com/explorer7-team/source/blob/main/README.md But Vista's explorer is still kinda broken with this tool for now

Compare it to the behavior of standard Windows Vista There is a chance you got very lucky in the silicon lottery and your particular CPU doesn't suffer from the drift bug.

OAuth2's purpose is to verify that you are not using an email client that is not trusted by Google (or Microsoft etc.) It is extremely difficult for small (usually open source) email client developer to get approval from Google, so supporting OAuth2 != being able to actually use it https://forum.palemoon.org/viewtopic.php?f=73&t=30566&start=20#p246217 So maybe consider switching the email provider. For example Polish email providers Onet and WP don't require OAuth2

Link for x64 version is dead

That's what happens when you copy-paste to avoid writing 3 words the second time and (don't) realize everything else is wrong

At least on some Broadcom WIFI+Bluetooth cards the Bluetooth part works as a USB device, so make sure you have working USB drivers, without them Bluetooth won't even show up in device manager. Or maybe try different USB drivers. I've had a HP branded Broadcom card working in Dell and Lenovo hardware so it should work with different brands as long as you install drivers through device manager

It is available if you install Windows 7 AIK, it is officially supported by Microsoft Someone in the MDL thread I linked recommended a newer Chinese modified DISM by Chuyu-Team for Vista (you have to login to view their post), but idk about that

It has been a long time ago since I last did that (now I have an ISO with integrated updates), and I didn't post a link, because back then I just deleted (running 7-zip file manager as Trutedinstaller) all amd64.something and x86.somenthing folders with the date modified matching what I wanted to delete. But while effective, that's not a proper way, as it may break your Turn Features on or off and possibly other things, Perhaps look at this: https://forums.mydigitallife.net/threads/how-to-peform-a-full-winsxs-cleanup-for-vista-and-windows-7-series.87379/

If you install KB4493730, than do restart to make sure it's installed than KB4474419, it should just install. First of all I would revert to a system restore point before installing updates that broke, because this reverting thing could have created a mess. Did you install all the earlier updates till 2017, If so: Quick search for this "Updates were not configured currently" shows that it can be caused by installing too many updates at once, so when installing updates try installing like 10 and than restart. If not, well, maybe those 2009-2017 updates and they are worth installing

The SHA-2 update (2019) updates most critical kernel files but doesn't update "all" files, so if you don't install other updates some of them may stay on let's say 2010 version insted of 2016. Is it a problem? It shouldn't be, but sometimes some system files expect files that they interact with to be in a fairly close version and they don't run well with too old ones. I remember I've ran into this issue once with Windows 7 To help cleaning the mess after installing updates read about cleaning up WinSxS

You can try looking for laptops with CPUs with NO integrated graphics (yes they do exist (i mean for sure 9300HF exists :) )) https://www.notebookcheck.net/Intel-Core-i5-9300HF-Processor-Benchmarks-and-Specs.462517.0.html And those can't possibly be running with Optimus. Weird AMD CPU + Nvidia combos like the one @Aiek link also look promising, but I'm not sure AMD + Nvidia immediately means that they are fine. But beware that those new Lenovo Legions with Intel 9300HF (and maybe AMD too) have touchpads restricted in ACPI to Windows 10+ and they don't even show up in device manager in Windows 8.1 and below https://msfn.org/board/topic/184465-intel-hid-event-filter-driver-with-modded-acpi-windows-7/

6002 is actually Vista service pack 2, 6001 would be sp1, and 6000 the original release. Officially however you need also all Vista updates till 2017 not just sp2. Some users reported success with only installing some updates (you need platform update and supplement for sure, but there are also others needed), but here are all of them, (you don't need hotfixes unless you are specifically affected by issues they fix and you also probably don't need Media Center TV pack etc.) https://msfn.org/board/topic/181756-windows-vista-update-repository-until-april-2017/?do=findComment&comment=1185620 You may need to get used to the bulk installations with scripts described there you are probably missing some updates

Actually also still works on Windows 2000 BWC ExK

Are you sure you ran bcdedit /set {current} nointegritychecks yes ? Here is how to do this post installation, but it's a bit harder that pre-installation https://msfn.org/board/topic/183046-guide-vista-extended-kernel-installation/?do=findComment&comment=1246958

I'm getting this "help protect..." on the mobile j2me youtube client Jtube which uses invidious (remote) proxy, and with TorBrowser "Sign in to confirm you’re not a bot" but not on JDownloader with my local ip