Any particular reason you want that exact version? I have 14.3 RU10 on Win7 working fine (except for the recent update problem-- definitions by LiveUpdate are not coming through)
People here said earlier that the particular version ( 14.3 RU7 Patch 3 ) is doing well with Windows 7 i.e. even for the updates!
Funny you should say that, I have a system that I updated from 14.3 RU4 to 14.3 RU10 and nothing changed. What version are you specifically running right now? I need to compare notes... Also, RU7 is essentially out of date, and some people are already chasing the second version (refresh-2) of RU10.
Is the SEP LiveUpdate feature working on your Win10 rig? I can't tell if it's a Win7 thing only or if more systems are affected. I have a W7 system with the older (but still maintained) v14.3 RU1 that worked fine until LU stopped functioning at the same time my other W7 unit with v14.3 RU4 got the error.
I ran this few days ago (2025-06-22), forgot to post. Sorry about that btw. This is on a Windows 7 Enterprise x64 production OS - there is no issues. Btw, no ESU updates installed (should not matter anyway)
Actually, you might be onto something. I agree it shouldn't matter, but what if the existence of ESU updates is suddenly conflicting with the Symantec LU link? I can't imagine why that would happen, but I've read enough reports of flaws with the new updates to not be surprised anymore. Also, all the systems on my end with the LU error have ESU updates (however, each one is a different degree of up-to-date and not in sync with a single month for the past year). I think next I should try pulling my reference VM images out to see if I can highlight any differences. Still, so weird though... Similar Windows 7 units with different ESU patch levels and different SEP versions sharing the same LU error... and you come along with a vanilla W7 system with SEP 14.3 RU7 (I actually tried that version but it didn't make any difference) and LU works fine for you. Even weirder, the LU error started this month, and the assigned W7 ESU updates for this month of 2025 are being reported to cause serious issues, but I haven't installed much of anything from ESU since the beginning of this year, ironically out of concern for exactly this case...
You could, and you might already tried it?, run CleanWipe from the tools section (remove everything) and reinstall SEP. It has always been a recommended solution in weird cases. It sounds weird and i share your thoughts. I have no insight with ESU so i'm kinda useless in that context. If members with, preferably, latest ESU updates could chime in that would be much appreciated. Kind regards
CleanWipe+Reinstall does nothing, as I mentioned earlier. I'm working on a non-ESU W7Pro VM right now, testing 14.3 RU6 first, then will move up to RU7 and RU10, then test with full ESU. Quickedit: preliminary findings not good; an early ESU update pack from the very first month of W7 ESU rollouts was on my first test VM as part of a test back when the bypass was being tested and, even with this one early ESU installed, SEP 14.3 RU6 still has LU error. This is gonna be a major catastrophe if SEP is that sensitive to ESU usage. Extra edit: I just realized my overuse of the word test and it's super cringe...o.0
RU5 is last version to support X86 If Broadcom is aligned with Microsoft they have to support this version.
Irrelevant, x86 is 32-bit (contrary to what the public has convinced itself that x86 somehow universally means x86-64). All my gear is x64 and my current system had SEP 14.3 RU4 (x64 edition) when the error hit. Now testing any other version that might work. RU10 x64 installs and mostly works on W7, but has the same LU error as RU1, RU4, RU6, and RU7.
Didn't you see the magnet link I left halfway up the page? Ya can't click it, but it can be added to your torrent client manually by copy & paste.