HP Pavilion g6 Notebook suffers from system crash upon sleep and hibernation. It's been an issue since the initial Windows 10, and still a problem even with AU update. Windows 7 machine, and all was well for this person. This person upgraded to Windows 10, and nothing but problems. I had to completely disable Sleep, and Hibernation modes, and remove the options. I also had to disable fast start-up feature. Everything is exceptional now except for the obvious, can't save energy. .. well I suppose it'll save a lot, now that raving is out of the equation
Is this troll bait? The bolded part is a very offensive addition to a statement that is no more valid than the privacy concerns (or whatever concerns) of the people you so casually and indirectly insult. Is it being a "shut-mind" to refuse using a product due to privacy concerns (the primary concerns levied against Windows 10), or any concerns? How does one define "shut-mind"-edness in the context of what an operating system should or should not do? Does this forum's policy allow you to insult others- however indirectly- with ad-hominem attacks?
The control concerns are another reason not to use Windows 10. The fact that there is less end user control with each "upgrade" of Windows 10 is a worrying trend and good reason not to upgrade or use Windows 10 at all. So far I haven't seen any benchmarks or anything factual to substantiate the claims of performance gain in the AU, just subjective impressions from posters who, obviously, already have a favorable view of Windows 10. Having to disable basic ACPI functions like sleep and hibernation is a good reason to reject an OS. Not only is this inconvenient, not having ACPI functioning properly can lead to overheating and premature hardware failure.
True I'm in favour of Windows 10. However, I wouldn't lie about the operation. As you can see I've posted about 10 driver & hardware issues. I've already upgraded quite a few machines to Windows 10 AU. Different hardware, software and configurations. I know how responsive the computers are before, and afterwards. I personally wouldn't exaggerate, and one doesn't need to anyways when its an obvious experiences. It's alright if I'm, and others being accused of lying. Anyways I agree with you that we are losing some controls. I don't like being limited, so you have one there.
@pegas Please post here if you have a breakthrough. If it is the Intel N7260 driver, it is surely not uncommon. I just got AU on WU so will try that tomorrow, maybe. If I still have the restart issue, I will try the ISO (with clean boot, wi-fi disabled). Also - I am interested, how did you upgrade, through WU, ISO, MCT or Windows Upgrade Assistant?
All I can say is I never got the chance to test the desktop. Windows no likey-likey VB environment. It will install but won't run.
I'm not saying anyone is lying about this. Subjective impressions are notoriously unreliable and easily influenced by a variety of factors including the overall opinion someone has about something. I don't doubt that these impressions are valid, it's just that a more responsive system could have nothing directly to do with the Windows software and could have just as easily been due to the update process doing a bit of system cleanup as it installed. Without rigorous testing and benchmarking of system processes affected by the update, there is no way to accurately verify any of this. The update process might of just run something equivalent to CCleaner on the system as it did the upgrade. It does completely reinstall the system, even in an upgrade. This is not the same as the older service pack installations which just replaced system files but left the OS in place. In any case, speed and responsiveness haven't been an issue on Windows 10, even on installs on older systems. The issues have been lack of control, privacy and software and driver incompatiblity.
I can only comment on mine and the family's machines to this regards. The machines I'm use to using, on a regular bases and maintaining. Based on my observations of those, I know that this Windows 10 AU is more responsive than the initial Windows 10 release, and faster than the November release. Also based on clean installs of Windows 10, and also upgrades. Even if Windows 10 installation is removing redundant files, and registry garbage relating to its OS. That in my book is still progress and enhancements by Microsoft, and makes still my observations accurate.
We should be worried about hours of operation than hours of idling. Computers aren't that fragile, if they were, It would be the hours of operation that would be worrisome. There are so many resource intensive uses that we do during operation than not.
I've installed AU on three computers so far. I did two upgrades and the third was a clean install. On all three computers AU, is running faster than the previous build. I have done no before and after benchmarking, but, I don't need to, as the increase in performance is very noticable, and is most definitely not a perceived speed increase.
One of the issues I had with a Windows 10 upgrade was a thermal shutdown during the upgrade process on a pair of laptops with both an integrated and discrete GPU. Part of the upgrade process (the part where there is a big circle with percentage completed) is done with a WinPE shell and the higher level ACPI throttling and temperature control functions are not in operation. The laptop would shutdown from overheating after the first or second reboot. Then the upgrade would fail and the old system restored. In one case, I let the laptop cool between reboots and succeeded after 3 attempts. In another, I disabled the discrete graphics GPU and hard throttled the processor in the BIOS to get the laptop to run cooler and let the upgrade work properly. This caused some driver issues after the upgrade when I restored the normal BIOS settings. There are some drivers I could live without but ACPI is not one of them. It is pretty fundamental to having the hardware work right. Sleep and hibernation not working are inconvenient but there might be other issues that are less obvious. If the CPU throttling and GPU switching is not working right, it could mean that the machine is running hotter than it needs to or, conversely, that it is throttled when it shouldn't be and not performing at its rated capacity.
I've kind of had a weird experience after updating to 1607. I used the MS update tool. In 1607, as opposed to 1511, everything seems slow; the context menu takes a few seconds to open, the taskbar notification area is often "blank", and applications are slower to respond. Does anyone else have that experience too? I reverted, and can verify that none of those issue are happening in 1511.
has anyone had a forced AU through Windows Update yet? after reading through all the problems I'm thinking i'll disable the update service for awhile, but I've left it on so far to keep 1511 up to date
Yes I used that method too. AU became available on WU yesterday, eight days after first release, along with cumulative update for 1511, which has been applied. So will try WU method to see if the restart / shutdown problem persists - after a backup image of 1511 . All upgrade methods should be the same, but maybe not. On my secondary machine, I tried various methods and only using ISO with clean boot, wi-fi disabled during install worked, so different methods seem to have different outcomes.
I believe the method is the same but what makes the difference are the conditions of update, you said it yourself - clean boot, network disabled etc.
Yes, I performed an upgrade on other laptop, since I can never do a clean setup there, and it was slow like hell. A normal maintenance (disk cleanup + component cleanup + 3rd party tools) fixed that, it runs just fine now.
I had a problem with the AU update and had to revert back to 1511 with an image. That was more than a week ago and the latest updates in Win 10 V 1511 never hinted about the AU. I think MS knows it is a bit premature to force AU as a normal update...
I updated and had to revert back as the AU really slowed my new Laptop down. reverted now all is well.
I tried to do a clean install of 1607, but gave up after the installer ran for 1 1/2 hours and hadn't even gotten past the "Getting Ready" screen... Super slow.
