Windows 10 Iot Enterprise 2016 Ltsb End Of Life
Vanina Mazzillo
I then re-installed WirelessSetup.exe and it installed with no issues. And I now have driver 20.70.23.1 from 3/21/21 installed with no issues. Newer WAP's at my work were no longer working with the old drivers from 2016. No idea why Intel felt it was necessary to limit the installer to newer versions of windows. LTSB is not end-of-life yet.
Open device manager, scroll down to network adapters and double click on your wireless nic, Intel Dual Bad Wireless-AC 8260 in my case. Go to the driver tab and choose update driver and choose browse for driver software on your computer. Paste in the location from earlier and make sure search subfolders is checked.
Yes, you can get the driver package to install, by hook or by crook, but there is a reason why it was not installing, namely that Intel does not test the new drivers with builds this old and thus blocked it from installing. Intel typically only validates with the current and three most-previous Windows 10 updates. The new build may work just fine, but Intel doesn't certify what it doesn't test. You are on your own using these newer, untested builds.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
Hi Everyone, I am having a weird issue with Norton on multiple computers running Windows 10 Enterprise LTSB, making me run Norton RnR every few days to get it working again. After I run RnR and get the older gray icon Norton back, everything is fine and working well. Then a few days later, it updates in the background to the new Norton 360 that uses the yellow icon. Everything is fine until I try to open Norton, If I double-click the desktop icon or tray icon to open Norton, NortonSecurity.exe will hang there using 25% of the CPU for hours and hours and hours not doing anything... until I restart the computer. I can't get Norton to open unless I run Norton RnR and reinstall which puts the older version back on my PC for a few days. Is there anything I can do to get this new version of Norton running? It works fine on my laptop running Windows 10 Home but will not work on LTSB.
Thank you so much for your reply and I really appreciate it! I have disabled fast startup on all my computers to try to avoid weird things like this. I should clarify that when I restart the computer, it only drops Norton's CPU usage back to 0 instead of hogging 25-30% of it all the time. Norton still doesn't open even after a restart and will start the infinite 25% CPU usage again without opening when I try to open it after a restart.
Hello again. I'm not sure whether you are in a home or corporate environment since the latter can be see while using a corporate issued device in a remote work environment. May we ask. What version and build of Windows are on computers affected? LTSB allows IT Admins to remain on older versions and builds that can save them the hassles of downtime, upgrades and updates that would otherwise take a ton of time and expense to perform. It may also not update the core of Windows in a manner that would keep third party software functioning properly. I'm wondering if your Windows version and current issues, fit that scenario.
Hello, thank you so much again for your advice! this is running in a home environment but I run them like it is a corporate environment except for having them joined to a domain. The computers are running Windows 10 Enterprise LTSB 2016 Edition version 1607 build 14393.0. I had some software that was not cooperating with windows updates a while back and was already running LTSB on a PC acting as a home server, so moved several other PCs over to it as well. I have not tried using the "remove only" option in Norton RnR yet, I will give that a try tomorrow as well as delete everything I can find Norton related on the PC and try again. I really appreciate the advice, and that is a good idea, my version of Windows 10 could be too old that Norton's code doesn't work anymore, although Microsoft is saying I have extended support until 2026. As far as GPO is concerned, I haven't made any changes to the default options that would affect antivirus and before this Norton update got released about a week or two ago, I have been running Norton fine for years.
I believe that since you are at least on the Windows 10 Anniversary Update, for the latest Norton to function correctly. Your Windows version isn't getting anything other than patches that Microsoft deems a risk to the Windows environment at large and nothing more feature wise. That is most likely the issue. Is Norton version 22.22.7.13 the version that causes your issue?
Could some mod deliver this issue to a developer? There're people that don't like the crappy updates that MS deploys. And there're people that are expecting a good customer service, specially since the last known good version (22.22.6.10) I had of Norton is the previous one to this new mess.
Your specific issue, as shown in your thread that you linked, is that you are also on an older version of Windows 10, but not on LTSB as the OP of the thread is having issues with. 1607 is not supported by Microsoft any longer which I am sure you are aware of, making it extremely vulnerable. Conversely, There have been a few Norton product releases after version 22.22.6.10, did you attempt to update in the past and had issues or just updating now? TIA.
Hello again and I really appreciate all of the replies! The Norton version I am having issues with is 22.22.7.14. That is the version identified in the file path to the executable. I might have had an issue with 22.22.7.13 as well but I'm not sure since I last opened Norton about two weeks ago and just realized the issue now.
Interestingly enough, I got this exact version of Norton (22.22.7.14) running just fine on an older computer running Windows 7 Enterprise. Of course it lost MS support back in 2020 but it looks like Norton still supports it. It's only my Windows 10 LTSB which it is having an issue with, which you're right, SA, it is basically only getting critical patches without the feature updates and I agree with you that is probably causing the issue. Especially since Norton works fine on my equally updated laptop running Windows 10 Home which gets all of the feature updates.
I also got a weird popup today saying that my current version of Norton 360 is not compatible with Windows 10. It then suggested downloading a version that is compatible with Windows 10 but that hung and never installed. When I do get the new version installed, on the shortcut to open Norton, it is adding a flag "/win8" at the end of the executable path, is it possible that when I am downloading Norton, their installer is identifying it as Windows 8 computer instead of Windows 10?
When install is completed, reboot!! Afterward, manually run live updates once and only once. You should get a patch that brings you to version 22.22.8.13. That is the current version on all my machines. Windows 10 and 11. Lets see if that makes any difference in the installation processes.
@SoulAsylum I mentioned MS updates due the fact that I'm still on a 2016 version. Windows 10 is awful in later versions, at least for me. To me it's clearly obvious that there's some kind of issues with the 2016 version, wheter the OP version or mine. It's the same behaviour and needs developer attention.
About the 22.22.8.13, I wish I could install it to try it, but it's nosense that we aren't able to download it manually to avoid things like this. The link you shared does nothing, and as I mentioned in my OG thread, if the version you're mentioning is 22.22.7.14, then is useless, because the moment I'm trying to install it as a new installation (I even deleted every old file), it will hang up at the "guy climbing a mountain" photo.
I completely removed Norton 360 from one of my computers running Windows 10 Enterprise LTSB using RnR, rebooted, and deleted every single folder I could find with Norton in the name including from C:\ProgramData\Norton, C:\ProgramData\NortonInstaller and C:\Users\Joe\AppData\LocalLow\Norton
I then downloaded DSP-N360-ESD-22.22.7.14-EN.exe from the link that you gave in your reply, SA. When I opened it, NortonSecurity.exe started after I accepted the UAC prompt and then started using 30% of the CPU constantly. Nothing ended up happening after a few hours with NortonSecurity.exe continuing to chew 30% of the CPU so I ended the process.
The old version I have been installing is from a cached installer on my computer called DSP-N360-ESD-22.20.5.39-EN.exe. I installed that and that installed just fine. I then rebooted and went through all of these versions through LiveUpdate one at a time:
I am really sorry to report back with the same thing and hopefully 22.22.8.13 will be released soon so I can try it manually. Unfortunately it looks like I am hitting a brick wall at this version with LiveUpdate.
Can I ask why you went through all those Norton versions instead of just logging into your Norton Account and clicking on Download to get the latest version to start? It is possible that as you start with the older version and then do the updates that there could be some 'garbage' left behind from the older versions.
Once a Microsoft operating system (OS) reaches the end of support, customers will no longer receive security updates. The OS may still work with programs and hardware after the sale or support of the operating system has been discontinued. However, the possibility increases that new programs and hardware will not be performant on an older OS. This frequently occurs because the manufacturers of new hardware and software make product-design decisions that take advantage of the increased functionality and features in newer operating systems. These manufacturers may decide to discontinue support of their products on older operating systems as appropriate.
d3342ee215