Recent content by ian50

I've seen these AOMEI giveaways before, as most have. Downloaded the backup zip file here, and as usual the activation key provided only lasts 1 year. I haven't bothered with any of the other applications as it is expected they will last only a year before purchase is necessary. This is all ok...

Brink shows how to pause updates for up to 20 years here: https://www.elevenforum.com/t/disable-automatic-windows-updates-in-windows-11.22669/ On my two Win 11 laptops, I've paused updates till 1/09/2045. I'm still able to download an update msu file and test it (provided I've done a backup...

Removed the expiration time limit Good !! The time bomb was bit of a worry. Now we have time to decide on free vs paid parameters without the Damocles Sword of suddenly being unable to recover in emergency. (As it stands, I use Macrium 8 paid, Aomei and Hasleo free - really not a hassle to...

Briefly, I've made a compromise on the vexed question of networking performing a faceplant on updates above 26100.4946/26200.4946. None of the suggestions made here to fix this (while all most gratefully received) had any effect whatsoever. Perhaps this note on compromise may help others still...

@pseymour Your comment 8:42pm If that is a reply to my earlier comment, it seems nonsensical. [Of course after updating, a reboot and logon has to occur] If you are referring to my comment, could you help clarify how the two are related ?

@Cameraman1995 Your comment 4:38pm This works with 26100.4946 and 26200.4946 (ie. 24H2 and 25H2) With updates more recent than 4946, the network still holds ok with only one network machine updated beyond 4946 (all machines still talk to each other as usual). With two or more network...

Amid the usual genuinely helpful comments on this 24H2 update, I can find no note on the network destruction wrought a few monrhs ago. So presumably, the network mess is now permanent. I've tried all the suggestions as assiduously as I may. None did anything to fix the problem (and I do thank...

@garlin Secure Boot changes are not enforced yet ... Thanks for that. Basically I can test the networking again when I find time without worrying about any other sneakily irreversible changes.

Two questions if anyone has approached them yet with this update: 1) does installation of KB5065789 (26100.6725) turn Secure Boot on irreversibly (ie. cannot then be reversed) ? 2) the preamble says that networking with SMB1 is herewith restored. This issue had half the world justly...

Apart from TinyWall and SimpleWall, I use FreeFirewall v 2.6.1 German programme, although in English. Very thorough, very granular, will block everything in or out except that which you specifically allow. Irrespective of those who believe MS plays by open rules, it squawks everytime it cannot...

As advised by Brink in an earlier tutorial: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings] "FlightSettingsMaxPauseDays"=dword:00001c84 Did it for me. No more updates until 1/09/2045. Yes, IF I allow an update to be installed, it may well delete that registry line. Then I'll...

As noted. I have two machines on Home 24H2 26100.4946 and one legacy machine on Win 11 Lite 23H2. The 26100.4946 MSU that I downloaded and installed did not contain the MS code that destroys Home networks that had no previous need of individual "credentials" for trusted network members...

This issue is all over the internet. I appreciate Bree's suggestions and help but none of these actually work. So I went on a long hunt through the net to glean information. (I'm trying to get 26100.5074 to behave itself. 26100.4946 is ok for the update I received). The best analysis I've found...

There are a large number of posts now on quite a number of threads dealing with the nasty way that MS has reconfigured networking from 24H2 26100.5710 onwards. Some people have found various network issues on 26100.4946. Although my small home network is ok on 26100.4946, I have found now that...

@glasskuter Thank you for your comment. I've tried the "give all machines on the network a credential" route without success. And even if it did work, with a dynamic IP address allocation on each boot, this has to be repeated. With machines on all versions beyond 26100.4946 (including 25H2...