Post by g***@aol.comPost by PaulPost by g***@aol.comPost by PaulPost by g***@aol.comI bought a used W/10-11 laptop and I don't have the sign in PIN.
I actually bought 2 and one had the PIN reset so I got into that one
OK.
I really don't care about the data on the one I can't get into but I
would like to be able to use it. Are there any tricks to get in?
Since these are identical laptops, I am really thinking about just
cloning the hard drive of the one I am into and laying that image down
on the other one. I just worry that there may be an activation issue.
I looked for a w/10-11 NG but I didn't see one.
I would do a Clean Install.
That way, the install serial number will be different
on the two machines.
The hardware serial number, is, at a minimum, the MAC address of the NIC.
But when you insert the DVD and do an install, a random
number is assigned as the software install serial number.
slmgr /dlv # dump particulars about installation
# "Installation ID"
Cloning a partition, would copy that number.
Now, I tested this, using the Insider Edition :-)
I installed, associated my MSA. Cloned the partition and
made a second C: drive on the same hard drive.
What I noticed, is any time the second OS did something
involving authentication, some "token" seemed to get
canceled, and I would be entering the password or pin,
more often as a result. I did this test case on purpose,
so that Microsoft telemetry would realize such a scenario
could arise (cloned C: ), and they should be ready for it.
Having identical install numbers, on identical DiskID numbers
or disk serial numbers, is a pretty unique situation, and
is the most pathological test case I could think of.
You can do what you like (whatever the software will allow),
but my personal preference would be a clean install.
Machines with a PIN still in place, could be stolen, but
I would guess you've thought of that. But users are clueless
enough, I can well imagine most people sell off machines
without de-authorizing them and taking the machine off the
"device list" against that MSA account.
I would be more concerned, if the machine was BIOS locked,
as an idiot user should be more aware of the need to
remove the password there. Some business machines, keep
the BIOS password in an eight pin serial EEPROM, and
removing the BIOS CR2032 battery, will not reset the
BIOS password for a business machine. And erasing the
EEPROM isn't enough either. A "pattern" goes in there,
even when it is "empty". If it's all zeros, the BIOS
may not start properly (as a "theft prevention move").
The manufacturer recommends "factory reset" in cases like
that. But I don't know if anyone has ever tested that method.
The "pattern" would be some sort of crypto.
Paul
Thanks Paul. It is what I expected. Since there is no key sticker on
this machine I am probably buying another W/10.
I may go another way. Since this came from a local company, I might
see if the last owner will give me the PIN.
When a machine is refurbished, a new key is cut which is
unique to the Win Refurbisher media. That key is supposed
to work, if you need to reinstall the OS.
Now, one problem with the Microsoft scheme for refurbishment,
is there is no new COA to be glued to the machine.
If the machine had received Windows 7 Refurbisher (like my
Optiplex 780 has on it), then the new key would be sitting
in the Registry. And using something like the MagicJellyBean
or the (Microsoft-hated) ProduKey, you may be able to dig that
up while the disk drive is slaved to your technician machine.
It's been a while since I've used Produkey, and I'd have to
use it on my Win7 machine (where Microsoft won't reach out and
trash ProduKey for me). One of the bean extractors, has the ability
to do more than the average one of them. Something like Belarc Advisor,
likely sticks to the boot drive for extractions of info.
If Windows 10 Refurbisher was installed (what a buyer would expect
in the late part of the year 2023), then the key is already now
registered with Microsoft. If Windows 10 is reinstalled (Refurbisher
version of not), then the OS should activate using the key recorded
on the Microsoft server (if the version was Pro, you'd reinstall Pro).
Now, presumably, the association with the previous owner would be broken,
once you apply an MSA account to the thing.
It is possible no other account was set up on the machine.
The Administrator account, does not have to be turned on,
so you cannot log in as the "Real Admin" unless the account
was on. If additional accounts were defined, they would be
available as icons on the lower left.
net user administrator /active:yes
Windows 10 used to be hack-able, by using the OSK.exe executable
and replacing it with CMD.exe . Then, you would attempt to use
the OSK at login time, this caused CMD.exe to pop up, and...
it runs with administrator privilege.
But then the question would be, what could we do about an
MSA, armed with such a tool ? My guess would be... not much.
Perhaps you could create a new local account, from that window.
and then log in from it. Or, maybe you could just turn on
Administrator, and when Administrator is listed on the
side of the screen, log in with that and do a whole
session as the Administrator.
But this assumes the hack works, and the OSK.exe one was closed
by Microsoft, and your machine is undoubtedly patched up far
enough, that the path is blocked.
An example of the idea, is presented here. But as time passes,
older attempts like this get blocked, so it remains to be seen
whether this still works. You could reset a local account with
tricks like this, and if you turn on the Real Admin, then an
extra icon presumably will show up on the left, at login.
https://4sysops.com/archives/reset-windows-10-password-by-disabling-windows-defender/
Once you boot in Non-Safe-Mode, I would expect Windows Defender
will remove any sort of hack of that class. (At least for Windows 10
it would. Probably not for Windows 7, but I really doubt you got
Windows 7 on those machines. That's against the T&C of the Refurbisher
product, that the installer-person has purchased.
Paul
I tracked down the owner and talked to him on the phone. There was no
refurb, they just sold them as is. These machines were used for a Jet
Ski and Beach Chair rental operation and he said there wasn't any data
there he cared about. The business is closed because of Hurricane Ian
a year ago. He gave me a PIN to try but it didn't work. He said he
might be able to track down the employee who had the machine but it
didn't sound like he was going to try very hard. I think I am going to
go with getting the disk ISO from MS and trying to reload it. I will
use the working W/10 machine since MS doesn't seem to support W/7 for
the media creation tool download.
Is it likely that the disk will pick up the key on a reload from
existing or should I go with that key retrieval program before I
start. I assume I can use it from the boot off the MS disk.
Right now the working machine is opened up on the bench waiting for a
disk drive cradle and cable to get a little extra breathing room.
C: is a 128g SSD and more than half full. There is a 2.5" drive slot
tho.
It had 4g RAM with an empty slot. I may throw another 8G at it for $30
but it seems OK now.
You can't download this on a Win10 machine which is running Windows Defender,
as it will be quarantined and declared "HackerWare", whatever that means.
It's possible a Win7 machine might download it. But once you have it,
if a "live Win10" gets a whiff, Windows Defender will be "at it". Using
a Windows installer DVD, and the Command Prompt window, might be a bit "safer".
I do not know if MagicJellyBean or Belarc Advisor receive this treatment from
Microsoft or not. The disclaimers of capability, don't look so good (I'm
not sure this will give a complete picture of your laptop).
https://www.nirsoft.net/utils/product_cd_key_viewer.html
"ProduKey is a small utility that displays the ProductID and the CD-Key of
Microsoft Office (Microsoft Office 2003, Microsoft Office 2007)
Windows (Including Windows 8/7/Vista)
Exchange Server
SQL Server
installed on your computer. You can view this information for your
current running operating system, or for another operating system/computer,
by using command-line options.
This utility can be useful if you lost the product key of your Windows/Office,
and you want to reinstall it on your computer.
ProduKey works on all versions of Windows. Both 32-bit and 64-bit systems are
supported. However, some features, like viewing the product keys of
another operating system instance, are only supported on Windows 2000/XP/2003/2008/Vista/7/8.
"
It's hard to tell whether it knows about ACPI MSDM or not, as MSDM started in Win8 era.
MSDM is used, for the OS that shipped on the laptop.
Keys like:
VK7JG-NPHTM-C97JM-9MPGT-3V66T (Windows 10 Professional) <--- X79
YTMG3-N6DKC-DKB77-7M9GH-8HVX7 (Windows 10 Home - multi language) <--- laptop!
BT79Q-G7N6G-PGBYW-4YWX6-6F4BT (Windows 10 Home - single language)
are place-holders when doing the Free Upgrade. The 3V66T one for example,
cannot be used in a reinstall. The presence of that one, means the
machine is registered with Microsoft, and a second attempt to install
Windows 10 will "just work". slmgr /dlv will reveal such an install
is automatically activated (should have activated status within a reboot
or two).
It's when a person buys a Win10 with Key, and installs the Key (say, while
the network cable is disconnected), that a "real key" value would show
in ProduKey. But in such cases, the key is still registered with Microsoft.
Sometimes, presentation of a "key", is to correct for confusion on the
Microsoft end. A user could buy a Win10 Home laptop (MSDM) and it would activate,
then install Win10 Pro (Key). Later, when they want to reinstall, using the Key
value might help with a reinstall of the Pro one. Otherwise, sometime weird might
happen when it considers the Home credentials.
The state diagram for what could happen, is of a fair size :-) Generally
you get the correct outcome, but... it's Microsoft.
This will list a few more tools.
https://alternativeto.net/software/produkey/
This might be the feature set I was thinking of.
https://alternativeto.net/software/showkeyplus/about/
The OP might have a sufficient fleet, to have a "good candidate"
for testing such tools (a machine with a Win10 MSDM, plus a purchased
Win10 Pro installed over top of the original Win10 Home, presenting
two key values for showkeyplus to print out.
I do so little key munging, there's hardly a reason to "keep a collection
and keep-em honed". My test cases here, just aren't good enough to
certify a tool for the hard cases.
*******
A 32-bit WinPE, can sometimes run 32-bit utilities. I have used a Macrium 32-bit
CD, to run something like HDTune. Not all utilities will run that way. Only some
of them. Originally, the WinPE might have not supported anything like that. I use
the 32-bit CD, because I've noticed more things work with 32-bit software,
than with 64-bit environments. That's why I have a 32-bit CD in the CD stack,
just for this purpose (potential of technician runtime environment). Maybe I
would test and see if a ShowKeyPlus could run from there. Most of the Macrium
CDs in the stack, are 64-bit ones.
Paul