Windows 10: Win10 will not run any .exe's I am migrating from my Win7 pc. WHATs THE FIX?

Win10 will not run any .exe's I am migrating from my Win7 (home) pc. It's useless until there's a fix! (I have OfficePro2019 on Win10 pc.) This goes back to 2015 and still no answer??

:)

 

WIN10 HOMEGROUP not accessible by WIN7 PCs

Hello,

I cannot connect my WIN 7(home) PCs (3 of them) to a homegoup created on a new Windows 10 (home) computer.

The WIN 7 PC see each other without any issue.

Here’s how I proceeded:

• Leave all homegroups on the WIN7 PCs
• Create a new homegroup on the WIN10 pc with the same group
• The WIN7 PCs see the new homegroup
• Click on join and enter password
• After some time I get a message that connection was not possible

I’ve also tried to create the homegroup on a WIN7 pc. The WIN10 pc can see and accept to join but the shares are not visible.



Running WIN 10 1709 HOME

 

USMT 10 - issues with profile when migrating from Win7 to Win10


Hello,

Has anyone used USMT 10 to migrate from Win7 to Win10?


I have used USMT successfully in the past to move WinXP (32-bit) to Win7 Pro (64-bit). I downloaded the new ADK to get the v10 tools. I now have USMT 10 and was practicing the migration of Win7 Pro 64-bit users to Win10 Enterprise 64-bit. Just for completeness, I also tried Win7 Enterprise 64-bit -> USMT -> Win10 Enterprise 64-bit. The results were the same.

I have used the original MIG XML files previously and they did what I needed, so I intended to do the same here. My XML files are unmodified at this point, but I tried with a few modifications aimed at not bringing over Start Menu (shared & user specific) *.LNK files.I have had this failure with both the "no LNK files" and stock XML versions. I tested and the migration logs (scanstate and loadstate) both claim no error in the migration process. Reviewing the logs I see no critical errors or warnings.

The problem is that following the migration, the profiles that were migrated cannot use Start Menu, Cortana/Search, Notification Area (Action Center), or right click any icon pinned to the Taskbar. SearchUI.exe appears to not be running when I review Task Manager -> Details. Cortana is not listed under Processes.

A new user - someone who logs on without a migrated profile - is created properly and they work normally. Existing users - the tech profile that existed prior to the migration - work fine. It is only a failure within the migrated profiles. I have tried the suggested Start Menu repair actions (the Get-AppXPackage / AppXManifest.xml process) and multiple other suggestions. Nothing seems to repair this, and since I can create a new profile successfully or use a non-migrated existing profile, I have to believe it's a flaw in what I'm doing with USMT.


My scanstate script is: scanstate.exe \\system\migration_folder /i:migapp.xml /i:migdocs.xml /o /uel:90 /l:C:\scanstate.log /v:13

My loadstate script is: loadstate.exe \\system\migration_folder /i:migapp.xml /i:c:\intel\usmtfiles\miguser.xml /l:C:\loadstatelog /v:13

 

Win10 Twice SLOWER than Win7 running data apps

We've a relatively high-horsepower dual boot pc which processes apps Twice+ as fast in Win7proX64 as compared to Win10proX64.

As example, we've a traditional Windows Desktop .exe built per C# VS2013pro targeting .NET4.5.2 which reads +1million records (40MB) from a text file, where:

_exe reads the text file (residing on resident ssd) in ~8seconds on subject Win7 boot.

_exe reads the text file (residing on same resident ssd) in ~21seconds on subject Win10 boot.

All non-OS variables equal and no other user launched apps.

Others running subject on independent systems report similar.

pc uses core_i7-2720QM @ 2.20GHz (8 cpu's), 16GBram;

ssd is ~500GB with >50% free;

exe is independently installed on each respective systems drive, However,

no significant difference if run from common drive.

pc boots ~quickly into Win7 or Win10; ie, this is not a start-up complaint.

Win7 and win10 at full current vers per MSupdate.

Why is win10 execution soooooo much slower ?

thx in advance.