The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
This is the thread for general chat.
Tell us how your day was, say hello or just introduce yourself if you're new to the site.
Post edited by Hmmm... on 29/12/2018 at 18:19.
Tell us how your day was, say hello or just introduce yourself if you're new to the site.
Post edited by Hmmm... on 29/12/2018 at 18:19.
Page:
DL wrote:
Exactomondo Chas :¬)
I, i.e Me, isn't the one sending the 'Magic Packet' ... it's an external source, out of our control, someone else, some nefarious external source ... like Microsoft;¬)
Noooo....
Again:
""The ability to wake from a hybrid shutdown state (S4) or a fully powered off state (S5) is unsupported in Windows 8 and above, and Windows Server 2012 and above. "
Your issue is elsewhere.
chasfh wrote:
And that is exactly the kind of equipment and software oddity I was referring to. What in hell is a "magic packet"?! Why would you need one, and for what possible reason would you need it to wake your PC when you weren't there?
Exactomondo Chas :¬)
I, i.e Me, isn't the one sending the 'Magic Packet' ... it's an external source, out of our control, someone else, some nefarious external source ... like Microsoft;¬)
DL wrote:
Ethernet device has an option to enable to receive 'Magic Packet' which has recently been citied as being a possible cause.
Post edited by DL on 28/10/2016 at 18:25.
And that is exactly the kind of equipment and software oddity I was referring to. What in hell is a "magic packet"?! Why would you need one, and for what possible reason would you need it to wake your PC when you weren't there?
I just looked this up. So internal networking then... and totally pointless in a home environment.
Probably also worth noting:
"The ability to wake from a hybrid shutdown state (S4) or a fully powered off state (S5) is unsupported in Windows 8 and above, and Windows Server 2012 and above. This is because of a change in the OS behavior which causes network adapters to be explicitly not armed for WOL when shutdown to these states occurs. WOL from a sleep state (S3) or non-hybrid hibernation state (S4) is supported."
So I'm also not entirely convinced by your magic packet theory.
Poltergeist seems far more likely...
Post edited by chasfh on 28/10/2016 at 18:52.
chasfh wrote:
As I said, some time ago I had a "sticky" switch in a case I was using, used to frequently cause my computer to "ghost start". There are also some motherboard and bios settings that can cause a similar thing, various other equipment errors and software "oddities".
In the past, this issue has been caused by software upgrades that have enabled 'hardware' items to 'wake' the PC, that is mouse, keyboard and even the ethernet driver and router. All these became 'enabled' following 1607 upgrade, they aren't now! Ethernet device has an option to enable to receive 'Magic Packet' which has recently been citied as being a possible cause.
Apart from that, I'm going with dav's "I suspect poltergeist." ;¬)
Post edited by DL on 28/10/2016 at 18:25.
DL wrote:
That much I can agree with and Active Hours was an addition with 1607, gone is ... 'Updates are available, do it when you like'. Came home from work the other day at 2.15 pm, machine had been off since 11pm the previous night, and the machine was on! It wasn't on when I left for work at 8.15am.
It's alright, DL I don't think you're going mad or anything! It's just that, as I said, if you're looking at Windows 10 as the culprit, you're probably looking in the wrong place.
The "Active Hours" thing doesn't mean "we'll randomly start your computer up when you're not looking", it means " we'll restart your computer when it looks like you're usually not doing anything". For this to work, your computer needs to be either:
a) On
b) Logged out but on standby.
As I said, some time ago I had a "sticky" switch in a case I was using, used to frequently cause my computer to "ghost start". There are also some motherboard and bios settings that can cause a similar thing, various other equipment errors and software "oddities".
chasfh wrote:
For example, my machine at work updates, and "suggests" 2 to 3 o'clock as an ideal time to restart (I take my lunch break around that time most days, so it's not an "active hour"). It doesn't start up on it's own overnight.
That much I can agree with and Active Hours was an addition with 1607, gone is ... 'Updates are available, do it when you like'. Came home from work the other day at 2.15 pm, machine had been off since 11pm the previous night, and the machine was on! It wasn't on when I left for work at 8.15am.
DL wrote:
That's just the point ... it didn't switch on before the 1607 upgrade! The Upgrade options have changed with the introduction of Active Hours which quite clearly state ... 'we will not restart your machine during these hours'
Post edited by DL on 28/10/2016 at 13:41.
The important part there is "restart" not "start". It doesn't do quite what you think...
For example, my machine at work updates, and "suggests" 2 to 3 o'clock as an ideal time to restart (I take my lunch break around that time most days, so it's not an "active hour"). It doesn't start up on it's own overnight.
I truly believe it's just coincidence that you happen to have updated Windows when the problem has surfaced.
chasfh wrote:
Other than that's nothing to do with Windows 10 "tweaks"; it's not a feature that's been added, I have several machines updated with the latest build and none of them spontaneously switch themselves on.
That's just the point ... it didn't switch on before the 1607 upgrade! The Upgrade options have changed with the introduction of Active Hours which quite clearly state ... 'we will not restart your machine during these hours'
Post edited by DL on 28/10/2016 at 13:41.
DL wrote:
Anyone have any ideas?
I suspect poltergeist.
DL wrote:
Morning all ...
A 'free' day today!! No work commitments ... just the usual home tasks like constructing shelving units for a family friend!
On other thing that is beginning to 'bug' me is the recent 'tweaks' that came with Windows 10 Anniversary Upgrade 1607 and the alterations to the Power Management/Update Options.
Since the upgrade, my PC has been switching itself on when it pleases at any time of day or night! I checked that all settings were set at Never and that no devices were allowed to start the PC! Upgrade options only include Active Hours which is pretty useless. Last night, for example the PC was switched off, I'd been in bed for an hour and it switched on ... on investigation no updates were installed, there was no reason for this to happen. Anyone have any ideas?
Other than that's nothing to do with Windows 10 "tweaks"; it's not a feature that's been added, I have several machines updated with the latest build and none of them spontaneously switch themselves on.
I'd suspect something else entirely, some other bit of software or hardware, (even a faulty case switch- had that once myself a long time ago!).
The last "spontaneous" start up I had was due to one of my cats finding the on- off switch and deciding that the little lights were pretty when you hit the button...
Page: