PCbanter

PCbanter (http://www.pcbanter.net/index.php)
-   Windows 10 Help Forum (http://www.pcbanter.net/forumdisplay.php?f=52)
-   -   Not complaining at all but? (http://www.pcbanter.net/showthread.php?t=1107318)

philo February 2nd 19 05:37 PM

Not complaining at all but?
 
I recently upgraded the last Win7 machine in my household to Win10.

It went smoothly and with one fix required for MS Word, it went very well.


The only thing that surprised me is when I checked activation, I saw
there was nothing I had to do...it already was activated.


Very nice but curious as to why.

Andy Burns[_6_] February 2nd 19 05:58 PM

Not complaining at all but?
 
philo wrote:

The only thing that surprised me is when I checked activation, I saw
there was nothing I had to do...it already was activated.


It seems pretty common for Microsoft's Win10 activation systems to "let
you get away with it" especially if the win7 was activated on an OEM
licence.

philo February 2nd 19 06:06 PM

Not complaining at all but?
 
On 2/2/19 10:58 AM, Andy Burns wrote:
philo wrote:

The only thing that surprised me is when I checked activation, I saw
there was nothing I had to do...it already was activated.


It seems pretty common for Microsoft's Win10 activation systems to "let
you get away with it" especially if the win7 was activated on an OEM
licence.




At any rate I was very pleased.

It was on my wife's main machine and when I was done, her desktop was
left exactly the way it was on Win7. Other than the tile option, I doubt
she would have known the difference.

😉 Good Guy 😉 February 2nd 19 06:09 PM

Not complaining at all but?
 
On 02/02/2019 16:37, philo wrote:
I recently upgraded the last Win7 machine in my household to Win10.

It went smoothly and with one fix required for MS Word, it went very
well.


The only thing that surprised me is when I checked activation, I saw
there was nothing I had to do...it already was activated.


Very nice but curious as to why.


Windows 10 is almost free for people to use it and enjoy as long as they
had Win7 upwards before. The deadline for free version passed a long
time ago but people are still reporting that the Microsoft servers are
still activating machines if they had previous activated products such
as 7 , 8 or 8.1. The AI is doing a great job.

Enjoy Windows 10.



--
With over 950 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.


Paul[_32_] February 2nd 19 07:56 PM

Not complaining at all but?
 
philo wrote:
On 2/2/19 10:58 AM, Andy Burns wrote:
philo wrote:

The only thing that surprised me is when I checked activation, I saw
there was nothing I had to do...it already was activated.


It seems pretty common for Microsoft's Win10 activation systems to
"let you get away with it" especially if the win7 was activated on an
OEM licence.




At any rate I was very pleased.

It was on my wife's main machine and when I was done, her desktop was
left exactly the way it was on Win7. Other than the tile option, I doubt
she would have known the difference.


There was a time when the "free upgrade" was aggressively
pushed, such that if Windows Update was running on Windows 7 SP1,
you could have a copy of Windows 10 "pushed" at you.

That program stopped on the appropriate date.

However, the activation that goes with it, did not. If
you do an Upgrade Install of current Windows 10 over an
activated copy of Windows 7 Sp1 or Windows 8.1, then
your copy would be instantly activated without typing
in any numbers. And that still seems to be working in 2019.
(I would expect it to stop when Windows 7 SP1 hits end of
life.)

If you install Windows 10 on a brand-new computer you built
at home, that never had an OS on it, then you'll get 30 days
grace before the OS will indicate a problem with activation.
Whereas some older OSes had a practice of rebooting (without
cleaning up) in the middle of a session on an expired
installation, Windows 10 seems to keep running. I have a copy
of Windows 10 in a VM (where it would not have seen a qualifying
OS), and it just shows the watermark in the corner every once
in a while. I haven't noticed it do a spontaneous reboot,
like in the old days. I have a copy of expired Windows 7 that
*does* reboot (it's an Enterprise SKU in a VM you can download
from Microsoft, that I run in VPC2007).

Paul

Nil[_5_] February 2nd 19 08:43 PM

Not complaining at all but?
 
On 02 Feb 2019, Paul wrote in
alt.comp.os.windows-10:

I have a copy of Windows 10 in a VM (where it would not have seen
a qualifying OS), and it just shows the watermark in the corner
every once in a while. I haven't noticed it do a spontaneous
reboot, like in the old days. I have a copy of expired Windows 7
that *does* reboot (it's an Enterprise SKU in a VM you can
download from Microsoft, that I run in VPC2007).


I have an unregistered copy of Win10 in a Virtualbox VM. It doesn't
do the reboot thing, and I don't think it ever will. As far as I can
tell it will run forever will most or all features working except
for any personalization - you can't change wallpaper or colors or
any of the visual customization stuff.

Paul[_32_] February 2nd 19 09:16 PM

Not complaining at all but?
 
Nil wrote:
On 02 Feb 2019, Paul wrote in
alt.comp.os.windows-10:

I have a copy of Windows 10 in a VM (where it would not have seen
a qualifying OS), and it just shows the watermark in the corner
every once in a while. I haven't noticed it do a spontaneous
reboot, like in the old days. I have a copy of expired Windows 7
that *does* reboot (it's an Enterprise SKU in a VM you can
download from Microsoft, that I run in VPC2007).


I have an unregistered copy of Win10 in a Virtualbox VM. It doesn't
do the reboot thing, and I don't think it ever will. As far as I can
tell it will run forever will most or all features working except
for any personalization - you can't change wallpaper or colors or
any of the visual customization stuff.


That's my impression too. That it's not nearly as aggressive
on activation issues as other OSes were.

The problem with most analysis of Windows 10 behavior, is
the "time horizon" issue. Many things on Windows 10, they
could come back to haunt you. How many days must you test,
to see whether a policy is in place ? I've tried to do
"Auto Upgrade" tests here, and not once has Windows Update
offered to upgrade a test case for me like it should.
Not once! I can leave setups configured for three months,
and boot them up occasionally, and the HDD installations (not VMs)
are just ignored like they weren't there.

That makes it pretty hard to reach any conclusions about
what a Microsoft policy might be, using test cases as
evidence. For example, I have an install set up right now
at 17134, where I disabled DOSVC using GPEDIT, and throttled
BITS (the original transport for Windows Update) to reduce
the number of connections if a Windows Upgrade is coming in.
It seems to be able to do Windows Update OK, but it doesn't
seem to want to upgrade the OS for me.

Maybe I should switch to one of my Insider setups and
abuse it and do tests with it. Because the Insider is
pretty relentless when a new version comes out.

Paul

philo February 2nd 19 10:12 PM

Not complaining at all but?
 
On 2/2/2019 12:56 PM, Paul wrote:
philo wrote:
On 2/2/19 10:58 AM, Andy Burns wrote:
philo wrote:

The only thing that surprised me is when I checked activation, I saw
there was nothing I had to do...it already was activated.

It seems pretty common for Microsoft's Win10 activation systems to
"let you get away with it" especially if the win7 was activated on an
OEM licence.




At any rate I was very pleased.

It was on my wife's main machine and when I was done, her desktop was
left exactly the way it was on Win7. Other than the tile option, I
doubt she would have known the difference.


There was a time when the "free upgrade" was aggressively
pushed, such that if Windows Update was running on Windows 7 SP1,
you could have a copy of Windows 10 "pushed" at you.

That program stopped on the appropriate date.

However, the activation that goes with it, did not. If
you do an Upgrade Install of current Windows 10 over an
activated copy of Windows 7 Sp1 or Windows 8.1, then
your copy would be instantly activated without typing
in any numbers. And that still seems to be working in 2019.
(I would expect it to stop when Windows 7 SP1 hits end of
life.)

If you install Windows 10 on a brand-new computer you built
at home, that never had an OS on it, then you'll get 30 days
grace before the OS will indicate a problem with activation.
Whereas some older OSes had a practice of rebooting (without
cleaning up) in the middle of a session on an expired
installation, Windows 10 seems to keep running. I have a copy
of Windows 10 in a VM (where it would not have seen a qualifying
OS), and it just shows the watermark in the corner every once
in a while. I haven't noticed it do a spontaneous reboot,
like in the old days. I have a copy of expired Windows 7 that
*does* reboot (it's an Enterprise SKU in a VM you can download
from Microsoft, that I run in VPC2007).

** Paul


Thanks Paul.

From what I can tell, even inactivated version of Win 10 will still
work...possibly not all features???

philo February 2nd 19 10:13 PM

Not complaining at all but?
 
On 2/2/2019 1:43 PM, Nil wrote:
On 02 Feb 2019, Paul wrote in
alt.comp.os.windows-10:

I have a copy of Windows 10 in a VM (where it would not have seen
a qualifying OS), and it just shows the watermark in the corner
every once in a while. I haven't noticed it do a spontaneous
reboot, like in the old days. I have a copy of expired Windows 7
that *does* reboot (it's an Enterprise SKU in a VM you can
download from Microsoft, that I run in VPC2007).


I have an unregistered copy of Win10 in a Virtualbox VM. It doesn't
do the reboot thing, and I don't think it ever will. As far as I can
tell it will run forever will most or all features working except
for any personalization - you can't change wallpaper or colors or
any of the visual customization stuff.



That seems a pretty minor thing to get a free operating system.

philo February 2nd 19 10:16 PM

Not complaining at all but?
 
On 2/2/2019 2:16 PM, Paul wrote:
Nil wrote:
On 02 Feb 2019, Paul wrote in
alt.comp.os.windows-10:
I have a copy of Windows 10 in a VM (where it would not have seen
a qualifying OS), and it just shows the watermark in the corner
every once in a while. I haven't noticed it do a spontaneous
reboot, like in the old days. I have a copy of expired Windows 7
that *does* reboot (it's an Enterprise SKU in a VM you can
download from Microsoft, that I run in VPC2007).


I have an unregistered copy of Win10 in a Virtualbox VM. It doesn't
do the reboot thing, and I don't think it ever will. As far as I can
tell it will run forever will most or all features working except
for any personalization - you can't change wallpaper or colors or
any of the visual customization stuff.


That's my impression too. That it's not nearly as aggressive
on activation issues as other OSes were.

The problem with most analysis of Windows 10 behavior, is
the "time horizon" issue. Many things on Windows 10, they
could come back to haunt you. How many days must you test,
to see whether a policy is in place ? I've tried to do
"Auto Upgrade" tests here, and not once has Windows Update
offered to upgrade a test case for me like it should.
Not once! I can leave setups configured for three months,
and boot them up occasionally, and the HDD installations (not VMs)
are just ignored like they weren't there.

That makes it pretty hard to reach any conclusions about
what a Microsoft policy might be, using test cases as
evidence. For example, I have an install set up right now
at 17134, where I disabled DOSVC using GPEDIT, and throttled
BITS (the original transport for Windows Update) to reduce
the number of connections if a Windows Upgrade is coming in.
It seems to be able to do Windows Update OK, but it doesn't
seem to want to upgrade the OS for me.

Maybe I should switch to one of my Insider setups and
abuse it and do tests with it. Because the Insider is
pretty relentless when a new version comes out.

Â*Â* Paul


I've been using activated Win10 part time since it was first released
and in general found it all works quite well. Upgrading the the next
version though takes some time...I generally assume ti may take 24 hours.

Andy Burns[_6_] February 2nd 19 10:27 PM

Not complaining at all but?
 
Paul wrote:

There was a time when the "free upgrade" was aggressively
pushed, such that if Windows Update was running on Windows 7 SP1,
you could have a copy of Windows 10 "pushed" at you.


This machine was purchased with Win10 Home, the predecessor machine had
Win7 Pro (but now has linux) I changed the product code on this machine
for the code from the sticker on the predecessor and it re-activated
with Win10 Pro.

😉 Good Guy 😉 February 2nd 19 10:42 PM

Not complaining at all but?
 
On 02/02/2019 21:27, Andy Burns wrote:

This machine was purchased with Win10 Home, the predecessor machine
had Win7 Pro (but now has linux) I changed the product code on this
machine for the code from the sticker on the predecessor and it
re-activated with Win10 Pro.


yes we always knew that there are thieves like you around still wasting
time trying to pirate a software that is almost free. Thieves have never
been known to be smart. There is a program about dumber thieves on
Quest so you must be in one of it.





--
With over 950 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.


philo February 3rd 19 11:33 PM

Not complaining at all but?
 
On 2/2/19 3:27 PM, Andy Burns wrote:
Paul wrote:

There was a time when the "free upgrade" was aggressively
pushed, such that if Windows Update was running on Windows 7 SP1,
you could have a copy of Windows 10 "pushed" at you.


This machine was purchased with Win10 Home, the predecessor machine had
Win7 Pro (but now has linux) I changed the product code on this machine
for the code from the sticker on the predecessor and it re-activated
with Win10 Pro.




I found that the MS server must recognize the HW.

I had a machine with an activated version of Win10 that I transplanted
into another machine. It needed to be activated for the new H/W.


When I later brought that first machine back into service and installed
Win10, it came up as activated.

Andy Burns[_6_] February 4th 19 05:49 AM

Not complaining at all but?
 
philo wrote:

When I later brought that first machine back into service and installed
Win10, it came up as activated.


I wouldn't risk having the same product key on the two machines, no need
in my case.

philo February 10th 19 09:16 PM

Not complaining at all but?
 
On 2/3/19 10:49 PM, Andy Burns wrote:
philo wrote:

When I later brought that first machine back into service and
installed Win10, it came up as activated.


I wouldn't risk having the same product key on the two machines, no need
in my case.




I'm a huge risk taker, once made a $2 bet on a horse and won.




All times are GMT +1. The time now is 11:09 PM.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright © 2004 - 2006 PCbanter
Comments are property of their posters