Restart loop after unsuccessful Windows 10 update

Do you see the problem I also had with version 1.83 BIOS.
I searched and searched.
Then that was too stupid for me and I revert to the previous BIOS version and everything worked again. That's enough for me. I want my z64 w to run with Win and that all new Win updates are up to date. I have now had 6 years of pleasure with the z64A at W.
 
SMorphin said:
Do you see the problem I also had with version 1.83 BIOS.
I searched and searched.
Then that was too stupid for me and I revert to the previous BIOS version and everything worked again. That's enough for me. I want my z64 w to run with Win and that all new Win updates are up to date. I have now had 6 years of pleasure with the z64A at W.
Click to expand...

Smorphin, thank you but party of what you wrote didn't work and a another party i just didn't understand (i'm not a very good geek). I have up and bought a Chromecast with Google tv.
Thank you all!!
 
Fat32 stick not higher,
EFI cannot use ntfs with some EFI BIOS.
Fat32 can only update up to 4GB Win Update if there are problems that cause problems in EFI Bios.
install old ver. update 05.2020 4GB Fat32+Upgrade+Upgrade.
 
Reduce with MinniToolPW or a USB WINPE stick. Your main partition put a new partition at 25 GB.
Install the last 4 GB Win 05.2020 update on it or on an external hard drive USB.
No drivers and do the latest build in Win as an upgrade to it and then install the drivers. It worked like that for me.
Hope with you too.
With Minnitool PW you can also mirror a complete system.
Or convert partition old MBR to GPT.
Or read partitions.
You only need entry BCD in Admin Input. bcdboot your part. Letter: \ Windows / s Enter your EFI startpart letter:.
Then you add your new Win Part ssd or usb to the Efi start menu.
 
Working with the Shell.
For example, enter the drive, BLK0: or 1 :,
on this drive you can see what is on it. The important thing is you have to look for the boat. When you are on the drive you can display the folder with ls.
Since it is EFI, you can only find the boot in the EFI folder.
So it has to show BLK1: EFI \.
there you will find a subfolder like Boot.
So you give BLK1: EFI \ Boot
if you want to see what's inside, enter ls again.
You can then boot EFI \ Boot \ bootia32.efi
All you really need to do is copy it down as it is.

Play it with Windows, again briefly.
EFI BIOs only recognize up to Fat 32
Then you also need a Fat32 USB stick
The last update in mind was over 4 GB.
Fat 32 only supports up to 4 GB.
This means you can only upgrade yourself via Windows.
So you have to install the last known Windows installation ISO under 4GB and then immediately upgrade to the new version.
Today's ISO installation new 05.2020 May update. In Win 09.2020 October upgrade.
It worked like this for me. You can install the drivers last.
With a new installation delete the whole system partitions except the Windows partition. You can overwrite this and the new Windows creates a Windows old folder.
This gives you the old files, but this Win is no longer executable.
 
SMorphin said:
Working with the Shell.
For example, enter the drive, BLK0: or 1 :,
on this drive you can see what is on it. The important thing is you have to look for the boat. When you are on the drive you can display the folder with ls.
Since it is EFI, you can only find the boot in the EFI folder.
So it has to show BLK1: EFI \.
there you will find a subfolder like Boot.
So you give BLK1: EFI \ Boot
if you want to see what's inside, enter ls again.
You can then boot EFI \ Boot \ bootia32.efi
All you really need to do is copy it down as it is.

Play it with Windows, again briefly.
EFI BIOs only recognize up to Fat 32
Then you also need a Fat32 USB stick
The last update in mind was over 4 GB.
Fat 32 only supports up to 4 GB.
This means you can only upgrade yourself via Windows.
So you have to install the last known Windows installation ISO under 4GB and then immediately upgrade to the new version.
Today's ISO installation new 05.2020 May update. In Win 09.2020 October upgrade.
It worked like this for me. You can install the drivers last.
With a new installation delete the whole system partitions except the Windows partition. You can overwrite this and the new Windows creates a Windows old folder.
This gives you the old files, but this Win is no longer executable.
Click to expand...

Smorphin, i very much appreciate how much you w want to help me, but i really don't understand the technical things you are saying. I only used my Minix as a streamer and i already bought the new Chromecast with Google tv and am very happy with it
 
Don't take it personally, I'll be happy to do it for you.
But your question will also be shown to others, so we both help others too.
Cu SMorphine
 
Hello ive been wondering if you guys have any files for me to download on my usb so i can load it into the uefi on the n64-w model, its bootlooping and erroring saying error installing windows, if you want to reinstall windows press ok
 
Install a Windows x86 to go on the stick with Rufus in Windows and a min 64 GB GPT format.
You can plug it in anywhere and start it in every EFI PC x86, but almost all x64, boot with the EFI start menu. Is there a nano stick, 3.1. costs around 12€. is only 2cm x 8mm in size.

If you want more, then take 128 GB nano Stick GPT.
In the Windows to go you install the Grub2Win Multi Bootloader on the stick, then you can also create more partitions on the stick for Linux systems.
It applies to 32 bit EFi Bios but 64 bit processor.
You have to install Win as a 32-bit system, you can create all other system partitions as a 64-bit system.
 
TacticalCookieYT said:
Hello ive been wondering if you guys have any files for me to download on my usb so i can load it into the uefi on the n64-w model, its bootlooping and erroring saying error installing windows, if you want to reinstall windows press ok
Click to expand...

Before you start messing around with wipes, uninstalls, reinstalls, etc......

Have you specifically tried booting Win into safe mode? If you can boot into safe mode it may allow you to roll back the most recent updates or driver installation, or troubleshoot further.

Or, is it looping before you can even access the boot menu?

Have you also tried simply removing all peripherals since the bootloop began, and then try another normal boot?

Sometimes it's a certain peripheral that can cause a bootloop after an update etc. If you can get a boot without any peripherals then you may be able to boot normally after that or roll back an update/driver.

Otherwise, are you getting a BSOD long enough to read an error code or error description as that may go a long way to helping too? Then, just do a search for the error code/descriptor with regards to potential causes and fixes.
 
You must log in or register to reply here.
Back
Top