Windows 10: You've got questions, I've got answers
-
Yes, except the problem didn't exist in Windows 7 when I got the upgraded version in July. It only started happening in Windows 10 which the September update was supposed to fix.
I recall that issue, so far i have been good.
-
-
I recall that issue, so far i have been good.
Wished there was a way to figure out what was doing it. LOL.
-
No problems on my end with the new version of windows 10 so far. Norton 360 is my antivirus protection,
-
Wished there was a way to figure out what was doing it. LOL.
Assuming you have newest version and having issues, thought you were just speaking for the other member.
-
-
Assuming you have newest version and having issues, thought you were just speaking for the other member.
Yes, have the new version but the problem started in Win10 sometime in August... I'm using Norton 360 Premier which got updated for Win10 in Win7 back in July. Some people who installed Win10 as a upgrade did get Norton uninstalled automatically. The only thing is by luck when I did my last in-place repair install, the disable autoprotect wasn't greyed out so I was able to disable it before doing the install.
-
Right. Explain why the new build 1115/10586 requires a 7m29s boot to get to the desktop? Where's the improvement? This is a disgrace!
Rather than point fingers, I'll state the obvious:
This isn't a common occurrence.
While it'd be nice if Windows was so bulletproof that this never happened to anyone, regardless of their hardware or software environments, I don't expect it to ever go that smoothly for all Windows machines.
If your installation is that screwed up, and nothing in Event Viewer tells you anything worthwhile, then you could consider a clean install. It's a lot of work, but it may be worthwhile if your troubleshooting skills are as limited as mine.
-
Yes, have the new version but the problem started in Win10 sometime in August... I'm using Norton 360 Premier which got updated for Win10 in Win7 back in July. Some people who installed Win10 as a upgrade did get Norton uninstalled automatically. The only thing is by luck when I did my last in-place repair install, the disable autoprotect wasn't greyed out so I was able to disable it before doing the install.
I feel more issues with those versions 360 and internet security then Norton Security the newer one, as those are not being really made anymore all just Norton Security now in name, they might still be updated but past product.
-
Rather than point fingers, I'll state the obvious:
This isn't a common occurrence.
While it'd be nice if Windows was so bulletproof that this never happened to anyone, regardless of their hardware or software environments, I don't expect it to ever go that smoothly for all Windows machines.
If your installation is that screwed up, and nothing in Event Viewer tells you anything worthwhile, then you could consider a clean install. It's a lot of work, but it may be worthwhile if your troubleshooting skills are as limited as mine.
And if you mess up the permissions for the files or folders like I did at one time, it can take 3 hours to even get the logon screen to show... And assuming you logged in, Settings and trying to add a new user will have the Please wait for 2 hours too. Lots of variables involved which the Windows installer will not fix.
-
I feel more issues with those versions 360 and internet security then Norton Security the newer one, as those are not being really made anymore all just Norton Security now in name, they might still be updated but past product.
Could be and it might depend on if the Norton product was installed before Windows 10 or after Windows 10. I have the full installer with the September update so for all I know, a uninstall and reinstall might fix it. And ofcourse the upgrades might not have upgraded as well as it should too as remember this is Symantec who before Norton 360 had issues with removal or else they wouldn't have that removal tool available.
-
-
Could be and it might depend on if the Norton product was installed before Windows 10 or after Windows 10. I have the full installer with the September update so for all I know, a uninstall and reinstall might fix it.
And if ever did a clean install or not and updated proper system drivers and other software on system. Say some of those older version are more problematic.