So I have to wait for new Version without timebomb? At the moment there is nothing newer than 26257. In place "Upgrade" from installed 26257 to 26100 using iso is possible although installed version has a newer build?
So I have to wait for new Version with extended timebomb? Later on after final Release I can switch to full version using in place update? Latest 2025 version is from july. Long time no news here from Microsoft.
come on, you can't switch to anything, you are on insider preview build, the next "release" should be in 4-5 years if you want something stable then clean install 26100 right now
@RobrPatty He probably used the typical SSV3/MMTool method, which is preferred for legacy Asus AMI BIOS images. You can't use it on newer UEFI-based AMI Aptio firmware.
I converted bios to .rom file & tool says not AMI bios error. So I loaded bios .cap file & tool says bios wrong size.???
@RobrPatty and @cbsvitzer Please don't deviate from the thread's original topic. A few posts earlier, I clearly mentioned that the SSV3/MMTool method is meant for legacy Asus BIOS images only. You can't use the method (or the tool) on Asus' UEFI firmware, period. Kindly do some research instead of beating a dead horse, or at least post in the correct section (e.g. BIOS mods).
Apologies for continuing this topic - but it may help other people that need to add/replace the new 2025 SLIC - see for example my post here on how to do it: https://forums.mydigitallife.net/th...e-dell-efi-bioses.13194/page-216#post-1826256 1. What works on modern ASUS BIOSes (B660, B760 I tested) is the modified Phoenix Tool v2.73 - i.e. you need to change "old" GUID ("A1902AB9-5394-45F2-857A-12824213EEFB" Unicode) for the module it looks for to the new GUID ("9E21FD93-9C72-4C15-8C4B-E77F1DB2D792" Unicode) in newer ASUS BIOSes and use as before. For security - just use HxD yourself to modify the PhoenixTool executable and use that for new BIOSes and keep the original for older BIOSes. 2. Please remember you need to wipe the old SLIC module data from the BIOS first - that is a bigger pain the proverbial - "Block 2" in general - I do it with the Windows AMI flasher. Unless you have a backup of the original BIOS without SLIC or know a better method...
Nothing has been fixed for so many months: - Ukrainian language pack still can't install, only Local Experience Packs (LXP); - Windows Defender takes so long to launch its interface and periodically says it is off (when it is on); - The RDP session slows down when connecting, it takes a certain amount of time to work properly; - There may be more to it, but I haven't looked into it more deeply.
Do you use Windows Server as a workstation? Because these updates did absolutely nothing in terms of server performance, no stability. And probably the funniest thing is that the first build is better than the updates that have come out. And such things are unacceptable, given the imminent release of this version. P.S. Also, it never ceases to amaze me how the company breaks things that worked perfectly even on Windows Server 2008, if not before.