Windows 10: Desktop flashing icons loop problem.

I think if you try an in-place upgrade install where the base language of the iso or whatever isn't the same as that of your installed OS you may get that a message like this one
"You can`t keep Windows settings, personal files, and apps because you`ve chosen to install Windows 10 using a different language than you`re currently using."

 

I think you are right about that. *Smile

 

Yes, that's right, but there's a way round it. My in-place upgrade to 1511 had to be EN-US because (despite my machine being for the UK market) it's initial free upgrade was for the US language. To avoid loosing my UK language packs (again) with the AU I wanted to change from EN-US to EN-GB.

The trick is a two step upgrade: first an in-place upgrade using the same base language as the existing OS. Second an in-place upgrade using the same version as the newly upgraded OS but in a different language. Both steps allow you to keep Windows settings, personal files, and apps.

 

Thanks. I tested your first suggestion in my backup pc and it worked fine stating I'm using English-US. Odd are my probem PC has the same. I tried it there to be 100% sure but it didn't work. The command line started with "x:" so I switched it to "c:" and entering "dism/online/get-intl" it said to go to the DISM log file, which I did and there was nothing there about the language.

Being a novice, I'm not sure what to do with your second suggestion. I entered variations of the "Langid ..." at the command prompt but but it said they weren't valid. I found this: Use the Language Pack Setup Tool to Install a Language Pack but I don't want to enter the wrong thing and make things worse. Will one of the suggested commands reveal the install language or just add/delete them? If it would work, what should the entry be to see the install language?

 

You may just as well simply try the in-place repair. If you think there may be two options, you have a 50% chance of succeeding with 1 download.

Note- there's always a chance the procedure may fail for other reasons... but we won't think about that - yet.

 

Hahaha. You were exactly correct! My first download attempt failed at almost 100% completion. 4.5 hours later the second attempt succeeded. I'm burning it to disk now.

I remember when I did the repair install with Windows 7, the process required several reboots and each time I had to be there to enter the logon password. Is there a way to turn off the password request via the boot menu or the troubleshooting feature?

 

How to Skip the Windows 10 Login Screen

Mm, long time for the download.. (I only use ADSL)

 

Thanks. That worked out. Now I'm read to do the repair install but the instructions state I have to disable the Secure Boot in UEFI. I'm pretty sure this was not necessary when I did the Win 7 repair-install. The tenforums instructions on how to disable it are a few years old and related to Windows 8. It says the specific motherboard has to be identified to match the correct disable instructions. I looked all over for what the specs of my motherboard are. All I can find is
Gateway Desktop PC DX Series DX4831-05 Intel Core i5 650 (3.20 GHz) 8 GB DDR3 1 TB HDD NVIDIA GeForce G310 Windows 7 Home Premium 64-bit, updated to Win 7 Ultimate 64 then Win10 Pro 64.

Other than Intel Core i5 650 I don't have any other information on the motherboard. I may be over complicating it but a more current explanation related to Win 10 seems better. I found this: How To Access UEFI Firmware Settingts In Windows 10 (7-31-15) Does it seem correct to you?

 

Hi, try this to check from windows if you have secure boot or not available, and its state:
Secure Boot - Confirm Enabled or Disabled in Windows 8

And if you don't have or use UEFI you won't have secure boot... which wouldn't normally apply to a PC supplied with Win 7- certainly not an older one.

(I've never even thought about that to be honest.. this laptop has it off by default, and my previous wasn't UEFI anyway!)

FWIW that tutorial is fine.. you can start the sequence from SHIFT + restart e.g. from a login screen. And it should work from Windows boot medium too- never tried.

 

That was very helpful. Good news - I think. Windows key + R to run dialog and entered msinfo32>System Information>System Summary, showed that Secure Boot State as "Unsupported". I take that to mean that the Secure Boot feature doesn't apply to this PC, as your suggested, and I don't need to worry about turning it off anymore. Correct? It mentions BIOS version/date as American Megaboards, Inc. PO1-A0, 11/17/2009.

 

Yes- that's perfectly reasonable.