All Activity

I tested adang1345's Python 3.14.0rc1 and was able to build and run yt-dlp on Windows 7 (in a VM snapshot). That should give us 5 years. Only issue: I had to compile the Brotli dependency myself, because it is not yet offered on PyPI. Cffi wheel for Python 3.14 was found here.

Hey guys, can I request a "restart" button around where check for updates is? The issue is that after some weeks of uptime suddenly start menu goes on top of everything - fullscreen games, apps, remote desktop, anything. Nothing helps: - changing all sort of options to make it refresh - killing and restarting explorer - changing position on screen/size/autohide, nothing Only if I check for updates and there is an update it downloads it and restart and that fixes it... till next time. So please can I have a smallish update with a button to restart it and I'll be happy again, because now it annoys the hell out of me sitting on top of my full screen programs/games

Well it would be nice, if they would provide some simple tools to analyze boot process - without some server / developer only blob and better error code handling.. ntbtlog.txt is far from good too, especially if they removed classic installation repair from the boot media.. and automatic registry backup is also disabled by default - as far if its not included within restore point itself. I dont even speak about bcd disaster.. which is really not good idea.. as its complicated object tree, unable to handle multi EFI parititon system, multiple files with Ids (1x boot\bcd, often cloned to windows partition too ; 3x (rescue bcd + rescue.xml) once on EFI partition, once in C:\Recovery and once in recovery Partition )., full of ids which are just made up from thin air, instead of using real partition IDs as Grub2, which at least had one text config file and more only if you are using autogenerating templates and its config files in etc/default/grub.. is not Otherwise if understand that diagram downgrade to MBR non UEFI and TPM install actually provide better logging.. I wonder its possible to use MBR booting - winload.exe instead of winload.efi on disk which is actually GPT? If i remember correctly i was using this with Windows 7 for quite a long time, but i tough that UEFI would be upgrade. It should be better with newer versions not worse, but they rather aim on start button position and new not backward compatible user interface API. So only real solution is make system partitions often.. with is not better in these days too, because every second application creating zillion of small cache files, instead of some big cache file.

Can I use this in a batch file : select volume G assign letter=A select volume D assign letter=T select volume E assign letter=U select volume F assign letter=D To change the DIsk letters? is it recommended to do this right before booting? Or in Boot.wim in winpeshl? To make sure it doesn't change it back? BTW I originally assigned the letters inside of Winpeshl.ini! using diskpart why did it change it? Thank you so far

... One should visit nicolaasjan's GitHub repo ; load latest yt-dlp release, https://github.com/nicolaasjan/yt-dlp/releases/latest then expand assets (if not expanded) and there they are : yt-dlp_win7.exe => 64-bit compile, yt-dlp_x86_win7.exe => 32-bit compile, BOTH are built on py3.13, so are good for the next 4 yrs, at least... Win7-compatible py3.13 courtesy of adang1345 ... Well, you didn't go through the GitHub issue I linked to ; there are automated solutions suggested such as this one : https://github.com/grqz/yt-dlp-getpot-jsi/blob/master/README.md @user57: https://www.python.org/downloads/release/python-31018/ is the latest py3.10 release by the PSF (security-only release in source-code form: https://www.python.org/ftp/python/3.10.18/Python-3.10.18.tar.xz ) Let me just say that achieving Vista SP2 (NT 6.0) compatibility should be much easier that targeting XP (NT 5.x); the last Vista compatible version was py3.7 (py3.4 for XP SP3). One should thoroughly comb the py3.10 source code and identify ALL the Vista breaking code the PSF authored after py3.7; these changes should then be reverted or rewritten with "translated" code that is py3.7 compatible; once that task has been completed, the modded source should then be compiled with a suitable compiler (MSVC and/or MSYS2) targeting NT 6.0 and, also, the 32-bit architecture; but this is NOT all ; yt-dlp itself has quite a large number of dependencies, i.e. Python modules; the py3.10 wheels for them to be found on PyPI are made with the official py3.10 in mind, so compatibility with a Vista-py3.10 isn't always a given, especially in the case when the modules contain C/C++ extensions (i.e. DLLs, which, under Windows, have the .pyd file extension); these Python modules have to be recompiled from their sources using the modded py3.10 and the same compiler that compiled py3.10 itself (probably on a Win10 host). Things on XP should be even more difficult because several py3.10 own dependencies, e.g. OpenSSL, have moved away from XP long time ago... https://github.com/adang1345/PythonWin7/blob/master/Notes.md#python-310 and https://github.com/adang1345/PythonWin7/tree/master/patches are adang1345's instructions on how to make py3.10 run on Win7; perhaps they'd be somehow useful for someone wanting to also attain NT 6.0 compatibility ... PS: the yt-dlp devs are adamant on always dropping a Python version once the PSF have dropped security support for that version (they're also keen on using the latest bells and whistles a new Python version comes with ) ; and the PSF always align themselves behind Microsoft when it comes to the Windows OS, so, as a result, only Win10+ is officially supported now ... PS2: Maroc's py3.11 offering previously discussed is what is called a binhack (binary hack): official DLL and EXE binaries are HexEdited and XP-incompatible functions are either stubbed or forwarded to a set of wrappers, mostly One-Core-API and/or Wine DLLs; the end result 1) makes my antivirus solution go completely berserk 2) WON'T even launch under Vista SP2 32-bit, as the wrapper DLLs specifically target NT 5.x system DLLs ...

its not a security measure, its security against the user or "non-microsoft" (if i remember right they had always a grude against a bootkit (even when it was totally legal)) so they decide what you do there - that would describe it right i would not call it security for that reason - its a missleading term that trys to confuse and lead it to a different discussion point its a old talk like about the monopol position microsoft is taken action for (not the first time) there was something like that even in very past times like with netscape - where microsoft where sued for taking monopol positions after that list they doing that then is very long - its litterally about billions of money where microsoft where sued for this surely this is about child-abuse or terrorism ? i dont think so - its just a company interest - calling out that is the same missleading term - if you would accept it like that you actually ruined yourself and fall for the trick

well it raise questions why they are not able to make it xp compatible, they are deeply into this stuff is it a problem of skill ? like somebody just used someones code that was wrote for win10, or a must to a certain engine version (that would also be a python version) it also could have come that python is a scriptish language like java - if you do write a code there it might just depents on the java engine personally i have never seen this to happen with a normal c++ style but going a little of-topic - this is bad for vista 7 and even 10 users - this version around play might just hit them at some point either - that might not be now but that would be a thing - they are trying with the vs2022 version already (and trying to get rid even 10) if it comes over a next newer python version then you run into the same problem - again it raise the question if you have insight into the real code - not just it´s low level/script functions

I didn't know that a Windows 7 program existed because it wasn't in his signature. They might not finish SABR before the end of Python. I don't want to do anything with Potoken because you need to dig it out of the browser repeatedly and then pass it into the command-line. I don't touch command line after initially setting it up.

First of all, have a read of below yt-dlp GitHub issue tracker comment: https://github.com/yt-dlp/yt-dlp/issues/13965#issuecomment-3168934752 Some of the described solutions may work for you (as they did for others ) ... At the same time, the yt-dlp devs are already working towards the (plausible) scenario of SABR-only: https://github.com/coletdjnz/yt-dlp-dev/tree/feat/youtube/sabr https://github.com/yt-dlp/yt-dlp/pull/13515#issue-3164587812 (latest test release, requires Win10+: https://github.com/coletdjnz/yt-dlp-dev/releases/tag/2025.08.10.010506 ) Since you're mostly on WS2008R2, the server edition of Win7, and @nicolaasjan already provides Win7-compatible (py > 3.9) yt-dlp compiles, you should be good to go when the currently experimental SABR downloader makes it, in due course, to the release branch of yt-dlp; Vista SP2 and XP SP3 users will be the ones "left stranded on a desert island" after October, because so far no solution has materialised for those users (i.e. a CPython >3.9 recompile/fork that would launch BOTH on NT 5.x/6.0, having additional support for all yt-dlp required Python modules ) ...

can you send a new link ,the download link is not working, thanks.

I will use this if it remains working after SABR remains the only option. Have to block advertisements though with a regular expression: obqj2.com will likely keep changing.

I have a 120Hz monitor and while games are indeed smoother than with 60FPS, On Windows 8, 7, and Vista, Aero animations still feel limited to 60FPS. Is it possible to make them actually utilize high refresh rate? or maybe make them 2x faster and increase their FPS that way?

Sadly it seems not all HD4000 are equal, some only support 4.0 while others support up to 4.4 To get the official Minecraft to run, it requires OPENGL 4.4, which one do you have? Also, you could try the last version of the graphics driver for HD4000 if you don't have that version already : https://www.intel.com/content/www/us/en/download/18606/intel-graphics-driver-for-windows-15-33.html

https://ssyoutube.online/privacy-policy

FYI: try the best online YouTube downloader so far. https://ssyoutube.online/en1/

Let's Get to the Facts 1. If I use StartAllBack in 2024, the problem doesn't occur. 2. If I use OpenShell, the problem doesn't occur. 3. I've already formatted my computer, thinking it was a problem, but the error persists. Based on questions 1 and 2, the problem is something that was changed in StartAllBack in 2025. See the video: StartAllBack settings are frozen, but all other programs continue to work. Only a few warn about the inability to locate the Windows taskbar. However, none of the settings are bugged like StartAllBack.

Yes, it's the bar under the icon (same location as the progress bar). It's true that with older versions of SAB, it was more noticeable (we're still using 3.9bb on Windows 11 24h2, which haven't been updated for some time) For this and especially for the progress bar which is much more beautiful

There's no hang in the dumps. Video makes no sense either, sorry. System is screwed up somehow, maybe there's a leak?

Well, I am glad it does the trick.

See the dump file in the link below. https://mega.nz/file/WJdAyAgI#NdECngrn-wkc-w9E_jC1AqmhsrHk8heHho204q6f1Cc https://mega.nz/file/jEs1GADb#2QEJ2rdQeVqkzAeXW7GNeYIzGGQj8QqqjSOfBymMhdk

I would like to put these lines in a batch file and run it through winpeshl.ini : in a file called os.bat DISM /Mount-Wim /wimfile:D:\path\to\boot.wim /index:2 /mountdir:C:\Mount reg load HKLM\TEMP C:\Mount\Windows\System32\config\SYSTEM reg add HKLM\TEMP\Setup /v "CmdLine" /t REG_SZ /d "X:\\sources\\setup.exe" /f reg unload HKLM\TEMP DISM /Unmount-Wim /mountdir:C:\Mount /commit in a batch file:mds @ECHO OFF :START MD " A:\Applications" MD " A:\Applications\Graphics\Adobe" MD " A:\Applications\Graphics\Corel" MD "A:\Applications\Graphics\Other" :End This in a text file call "partitions.txt" sel dis 0 cle Convert GPT cre par efi size=260 for quick fs=fat32 label="System" a** letter="S" cre par msr size=16 a batch file call : diskpart.bat %SYSTEMDRIVE%\Windows\System32\diskpart.exe, "/s %SYSTEMDRIVE%\Windows\System32\partitions.txt" strartnet.cmd: reg add "HKLM\SYSTEM\Setup\LabConfig" /f /v "BypassTPMCheck" /t REG_DWORD /d 1 reg add "HKLM\SYSTEM\Setup\LabConfig" /f /v "BypassSecureBootCheck" /t REG_DWORD /d 1 reg add "HKLM\SYSTEM\Setup\LabConfig" /f /v "BypassRAMCheck" /t REG_DWORD /d 1 All this stuff will go into boot:2[boot]. could someone put it into the proper order and show where this goes? Dism /apply-image /imagefile:%usbletter%:\sources\install.wim /index:6 /ApplyDir:C:\ bcdboot c:\windows /s S: /f all lang,bat Dism /mount-image /imagefile:C:\my_distribution\sources\boot.wim /index:2 /mountdir:C:\Mount\boot Dism /image:C:\mount\boot /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\fr-fr\lp.cab" Dism /unmount-image /mountdir:C:\mount\boot /commit All this stuff will go into boot:2[boot]. could someone put it into the proper order and show where this goes? Thank your for your help

https://github.com/mifi/lossless-cut

Sure but it should be able to work for those who do want it.

Below I detail some peculiarities I've found in the most reliable tools. I completely rule out any others not mentioned. SPECIAL FEATURES OF OFFICIAL TOOLS Windows 2000 Disk Management: -Initializes MBR disks + 2 TiB -Creates MBR partitions larger than 2 TiB -Only aligns to sector 63 -Does not format FAT32 partitions larger than 32 GiB Windows XP Disk Management: -Initializes MBR disks + 2 TiB -Does not create MBR partitions larger than 2 TiB -Only aligns to sector 63 -Does not format FAT32 partitions larger than 32 GiB Windows Seven Disk Management: -Initializes MBR disks + 2 TiB -Does not create MBR partitions larger than 2 TiB -Only allows you to use the first 2 TiB of an MBR hard disk. DiskPart.exe in Windows 2000 -Does not exist. DiskPart.exe in XP -Does not initialize MBR disks +2 TiB -Does create partitions +2 TiB -Only aligns to sector 63. -Does not format any type of partition (it does not have the format command). -Requires exiting the program to work without errors with other programs, since the disks appear as mounted in it. DiskPart.exe in Windows Seven -Initializes MBR disks +2 TiB -Does not create MBR partitions larger than 2 TiB. -Requires exiting the program to work without errors with other programs, since the disks appear as mounted in it. Note: To use third-party programs, you must first exit Diskpart with the "exit" command, or the disks will remain mounted, generating errors in other programs. SPECIAL FEATURES OF THIRD-PARTY TOOLS Acronis Disk Director: -It is linked to the operating system's Disk Manager. -Partition alignment depends on the operating system; in XP, they are aligned to sector 63 and in Windows 7 to sector 256. -When expanding a FAT32 partition created with "MiniTool Partition Wizard 9.2" by using the free space left behind, the partition appears marked as "Damaged" in DiskGenius. -It does not support cluster sizes greater than 64 KB. DiskGenius: -It does not have a separate option to initialize the hard drive or leave it in its initial state. -When creating partitions on an MBR +2TB hard disk, without prior initialization, the drive letter is not visible in Windows XP, but it is visible in Windows 7 (it requires a separate initialization). EaseUS Partition Master -There is no separate option to initialize the hard drive or leave it in an initial state. -It does not allow creating +2 TiB partitions on MBR hard drives. FAT32 Format -Does not support cluster sizes greater than 64 KB Macrorit Partition Expert -Initializes MBR + 2 KB disks -Only aligns to sector 384. -There is a section that says "SSD partition alignment," expressed as a number plus the letter K, giving these options: Optimized, 4 KB, 8 KB, 16 KB, 32 KB, 64 KB, 128 KB, 256 KB, 512 KB. I don't know what its function is; any value selected on a hard drive with a 4096-byte logical sector results in the partition starting at sector 384. The help says: 4 KB is recommended for partitions smaller than 1 TB, 32 KB for 2 TB, and 64 KB for 3 TB and larger. https://macrorit.com/partition-magic-manager/how-to-align-ssd-partition.html I have found that either value gives the same result for the start and end sectors and cluster size on a mechanical disk. MiniTool Partition Wizard -There is no separate option to initialize the hard drive or leave it in its initial state. -When creating partitions, the alignment mode defaults to "Align to Cylinder" instead of "Align to MB." You must specify MB manually. (Align to cylinder is to sector 63 / Align to MB is to sector 256) -When creating partitions on an MBR +2TB hard disk, without prior initialization, the drive letter is not visible in Windows XP, but it is visible in Windows 7 (it requires a separate initialization). -Creating a single FAT32 partition on an 8 TB MBR hard drive leaves 9 MB of free space at the end, which is only visible with Acronis Disk Director 12.5 (if expanded with Acronis, the partition appears marked as "Damaged" in DiskGenius; formatting it with DiskGenius now shows it as OK). Paragon Partition Manager -There is no separate option to initialize the hard disk or leave it in an initial state. -Cluster sizes greater than 64 KB are not supported.

I've found that some partitions larger than 2 TiB created from Windows Seven are not visible in XP. Perhaps this is why some users consider the limit for MBR partitions to be 2 TiB. The problem is that official tools don't allow this, and third-party tools that don't have options to initialize new hard disks operate strangely on hard drives with 4096 bytes logical sectors. These tools don't measure the hard drive capacity, but rather the number of sectors. This happens at least with Eassos Disk Genius and MiniTool Partition Wizard, these consider the following: - All hard drives up to 16 TiB are considered MBR unless these are first converted to GPT. -They work incorrectly with a +2TiB hard drive if it is not initialized as MBR, since by default these consider it already initialized as MBR. - If partitions smaller than 2 TiB are created, these may be visible in XP. - After creating partitions larger than 2 TiB on an uninitialized hard disk with these tools, they are not visible in Windows XP, but they are visible in Windows Seven. This is why I decided to write these instructions for creating partitions larger than 2 TiB from Windows XP. Incidentally, in the latest Windows Eleven update, Microsoft has increased the official limit for FAT32 partitions from 32 GiB to 2 TiB, although I have managed to create them from XP without any problems, up to 16 TiB. First, we need to connect the hard drive with an adapter that informs XP of a logical sector size of 4096 bytes, for example, a USB-SATA adapter whose firmware provides this feature. More info here: https://msfn.org/board/topic/186645-devices-list-compatibles-mbr-hard-disk-2tb/ STEPS: 1. Clean the disk with Macrorit Partition Expert using the "Clean Up Disk" option. (equivalent to leaving it in factory settings) Alternatively, use the "clean" command in DiskPart or Acronis Disk Director 12.5. 2. Initialize the disk with Macrorit Partition Expert using the "Initialize" option. Alternatively, initialize the hard drive from the Windows XP Disk Management or with the program Acronis Disk Director 12.5. 3. Create the partitions. For NTFS, create the partitions with Eassos Disk Genius 5.6.0.1565. For FAT32, create the partitions with Macrorit Partition Expert 8.6.0, if you find it appropriate to start the partitions at sector 384. Once created with Macrorit, these can be resized with DiskGenius to any size and sector start. (Acronis does not support cluster sizes greater than 64 KB, and MiniTool leaves a 9 KB space at the end of the partition.) 4. Verify that the partitions appear in My Computer. If these don't appear, check the hard drive for any errors in Windows XP's Disk Management: -If it doesn't show an error, restart the system so that the partitions appear in My Computer and in Disk Management. -If it clearly shows an error, repeat the steps using alternative programs or another version of the Windows operating system. -If you're using another version of Windows, verify that the partitions are visible in XP before writing data. 5. The alignment results can be obtained in XP with the "wmic partition get Name,StartingOffset,Size" command, taking the values and dividing by 4096, or using MiniTool Partition Wizard 10.3 Professional with the "verify alignment" option. Conclusion: Always initialize hard disks with a specific tool that allows it before working with them.