Can I install new Win10 pro over existing one?

I'm prepared to buy a Win10pro disk and dump it over my present
installation to stop the Search error...
"The Windows Search service terminated unexpectedly. It has done this
39 time(s)."

Other small errors keep appearing.

Also, can I dump registry values over from my other Win10 OS (on this
same motherboard), which has no errors, onto the above?

Peter

Peter Jason wrote:
I'm prepared to buy a Win10pro disk and dump it over my present
installation to stop the Search error...
"The Windows Search service terminated unexpectedly. It has done this
39 time(s)."

Other small errors keep appearing.

Also, can I dump registry values over from my other Win10 OS (on this
same motherboard), which has no errors, onto the above?

Peter

http://answers.microsoft.com/en-us/w...943440a?auth=1

"I fixed the problem with Windows Search service not starting by doing the following:

1. Open Registry Editor (Start Type regedit and press enter)
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search
3. Double click SetupCompletedSuccessfully
4. Change it from a 1 to a 0.

Windows Search service then started and
all the errors in the Event Viewer no longer appeared.
"

I presume what that does, is re-initialize C:\ProgramData\Microsoft\Search\Data\Applications\ Windows
(home of Windows.edb, the most fragmented file on the computer). Agent Ransack couldn't
find it, because of a mild permissions problem. On a default setup,
the .edb is 25MB, while used for serious indexing, the file
is around a gigabyte or so (and has hundreds of fragments).

*******

You can Repair Install the OS, by running Setup.exe off the
DVD while the OS is already running. The Repair then builds
on the existing registry state. For Windows Pro over Windows Pro,
I don't expect any surprises (if this is the Free Upgrade,
your Digital Entitlement will serve to activate it).

For other combinations, you can look at some of the voodoo here.
A key ending in "...3V66T" ? They have to be joking. Now,
how many times have I fallen for that this year.

http://www.zdnet.com/article/going-p...thout-hassles/

*******

I don't recommend bringing a set of registry files from
another machine, because it will not "align" with your
current setup. The only sound you're going to hear, is
"kaboom". You need some sort of Laplink PCMover or the like.
Which would move applications from the other machine, as
well as the associated registry settings.

https://en.wikipedia.org/wiki/Laplink_PCmover

That's the only product line I know of that comes
remotely close to "bringing stuff from another PC".

If my PC is fouling up, I'm generally pretty happy
to just clean install. Knowing that all the bad
karma will be left behind in the bitbucket. The
setup I'm typing on, was clean installed two months
ago, because I got fed up trying to fix my Ordinal65
bug.

*******

To fix your hidden partition needing CHKDSK:

The general principle involved:

1) Use a Linux LiveCD and Terminal to do

sudo fdisk /dev/sda

and set the 0x27 hidden partition (with CHKDSK damage)
to 0x07. Write the new value and exit.

If the disk is GPT, I haven't a clue what tool works
with GPT disks.

2) Boot Windows and do CHKDSK on the partition.

3) Repeat step i, changing 0x07 back to 0x27.

A side effect of the change, is the OS will
list an additional volume in the Optimize dialog
(the defragmenter), which of course cannot be seen now,
because it's invisible again.

The CHKDSK in step 2 should fix the corruption.

I know this, because I've been in there :-)
I think this is the thing that needs CHKDSK.
The partition is 450MB in size.

https://s15.postimg.io/pwvs3fee3/recovery_partition.gif

You can also "unhook" that partition, and then
I don't see a reason for Windows to ever look in
there again. This posting is on a similar topic,
involving working with the 450MB partition.

http://al.howardknight.net/msgid.cgi...nt-email.me%3E

I still don't have a replacement download source for
PTEDIT32.exe, which would be the preferred way of
making the 450MB partition visible. Symantec offered
it for download for years, but removed it last year
some time.

Paul

Paul wrote:

If my PC is fouling up, I'm generally pretty happy
to just clean install. Knowing that all the bad
karma will be left behind in the bitbucket. The
setup I'm typing on, was clean installed two months
ago, because I got fed up trying to fix my Ordinal65
bug.

You are not using Macrium Reflect?

John Doe wrote:
Paul wrote:

If my PC is fouling up, I'm generally pretty happy
to just clean install. Knowing that all the bad
karma will be left behind in the bitbucket. The
setup I'm typing on, was clean installed two months
ago, because I got fed up trying to fix my Ordinal65
bug.

You are not using Macrium Reflect?

If I had the choice between "dragging a registry file set
from another PC" versus Clean Install, I'm saying I would
pick Clean Install.

For long-standing bugs, for which *no* backup contains
an uncontaminated solution, sometimes you do have to
reinstall. Even after reinstallation of WinXP, my
shell32rdinal65 Explorer crash is still present.
It is a function of installed software. An interaction
between VPC2007, the RAMDisk software (which insists on
marking the RAMDisk partition as "Active" or bootable),
and some game software. When I start the game, File Explorer
crashes. It may require one usage of VPC2007 during
the day, to "promote" the crash. The crash is
"harvested" when the game plays. The crash will
not happen more than once a day (it is time sensitive,
happens after midnight etc).

In any case, if I reinstall the programs in question,
the same damn problem shows up.

How would you fix that one ? Change OS version ? :-)

I'm at a loss as to what debugging tool to try next.
I've watched it in Procmon (I caught it once), and
there is what looks like "disk scanning" going on,
right before the crash. And I cannot figure out
why the software in question is doing this "disk scanning".
It's unusual behavior. I have no clue what it is looking
for. It would be like if you caught Notepad scanning
your C: drive, a totally unexplained behavior. And
while that scanning is going on, when it scans the RAMDisk,
it gets the ordinal65 crash (because a RAMDisk does not
"look or smell" like a hard drive).

Paul

In article
Paul wrote:

If I had the choice between "dragging a registry file set
from another PC" versus Clean Install, I'm saying I would
pick Clean Install.

This will never work. Registry files are machine/install specific.
Many things will be broken if you try this. Quite possibly booting
will not complete.

On 01/09/2016 23:12, Peter Jason wrote:
I'm prepared to buy a Win10pro disk and dump it over my present
installation to stop the Search error...

What made you think that 10-Pro will do what you want to do?

Second, to convert Home to Pro is by simply changing/inserting the new
serial number. There is no need to install anything again. Windows 10
is smart enough to reconfigure the machine when a new serial is inserted.

To test anything, just enter this serial number and see if it works on
your machine:

VK7JG-NPHTM-C97JM-9MPGT-3V66T

Please note that when you insert the above key, your system will convert
to Prof but it won't activate until you enter the correct/valid retail
key. There is no going back to Home from above conversion so make sure
you have backups done before doing anything. This is the standard
method of conversion for most people!!.




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