shutdown –r –t 10 => reboot in 10 sec
shutdown –s –t 30 => shutdown after 30 sec
shutdown –r –t 10 => reboot in 10 sec
shutdown –s –t 30 => shutdown after 30 sec
https://thegeekpage.com/turn-windows-features-on-or-off-blank-or-empty/
https://softwarekeep.com/help-center/how-to-fix-windows-resource-protection-could-not-start-the-repair-service
C:\Windows\system32>sfc /scannow
Windows Resource Protection could not start the repair service.
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 33% complete.
C:\Windows\system32>Dism /online /Get-Features /format:table | find "SMB1Protocol"
SMB1Protocol | Enabled
SMB1Protocol-Client | Enabled
SMB1Protocol-Server | Enabled
SMB1Protocol-Deprecation | Enabled
SMB1Protocol can be enabled in Turn Windows Features On / Off.
Enabled SMB 1.0/CIFS Client, which made Windows 10 see all network PCs with Error code 0x80070035.
FOLLOWING COMMAND SOLVED the problem and gave access to shares:
C:\Windows\system32>
reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters /v AllowInsecureGuestAuth /t reg_dword /d 00000001 /f
https://winitpro.ru/index.php/2018/05/16/0x80070035-ne-najden-setevoj-put-windows-10/
sudo flashrom -p internal
flashrom v1.2 on Linux 5.19.0-15-generic (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found chipset "Intel H170".
This chipset is marked as untested. If you are using an up-to-date version
of flashrom *and* were (not) able to successfully update your firmware with it,
then please email a report to flashrom@flashrom.org including a verbose (-V) log.
Thank you!
Enabling flash write... Warning: BIOS region SMM protection is enabled!
Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed.
New value is 0xaa.
SPI Configuration is locked down.
FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
FREG2: Management Engine region (0x00003000-0x0027ffff) is locked.
Not all flash regions are freely accessible by flashrom. This is most likely
due to an active ME. Please see https://flashrom.org/ME for details.
At least some flash regions are read protected. You have to use a flash
layout and include only accessible regions. For write operations, you'll
additionally need the --noverify-all switch. See manpage for more details.
Enabling hardware sequencing because some important opcode is locked.
PROBLEMS, continuing anyway
Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.
No operations were specified.
-------------------------------------------------------------------------------
sudo flashrom -p internal -r /home/bk1.bin
flashrom v1.2 on Linux 5.19.0-15-generic (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found chipset "Intel H170".
This chipset is marked as untested. If you are using an up-to-date version
of flashrom *and* were (not) able to successfully update your firmware with it,
then please email a report to flashrom@flashrom.org including a verbose (-V) log.
Thank you!
Enabling flash write... Warning: BIOS region SMM protection is enabled!
Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed.
New value is 0xaa.
SPI Configuration is locked down.
FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
FREG2: Management Engine region (0x00003000-0x0027ffff) is locked.
Not all flash regions are freely accessible by flashrom. This is most likely
due to an active ME. Please see https://flashrom.org/ME for details.
At least some flash regions are read protected. You have to use a flash
layout and include only accessible regions. For write operations, you'll
additionally need the --noverify-all switch. See manpage for more details.
Enabling hardware sequencing because some important opcode is locked.
PROBLEMS, continuing anyway
Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.
Reading flash... Transaction error between offset 0x00003000 and 0x0000303f (= 0x00003000 + 63)!
Read operation failed!
FAILED.
-------------------------------------------------------------------------------
sudo flashrom --programmer internal -r /home/bk1.bin -i bios --ifd
sudo flashrom -p internal -r /home/bk2.bin -i bios --ifd
sudo flashrom -p internal -r /home/bk3.bin -i bios --ifd
sudo flashrom -p internal -r /home/bk4.bin -i bios --ifd
sudo flashrom -p internal -v /home/bk4.bin -i bios --ifd
md5sum bk1.bin bk2.bin bk3.bin bk4.bin a3403.bin
8dccbad887dc112574a8999713029b7a bk1.bin
8dccbad887dc112574a8999713029b7a bk2.bin
8dccbad887dc112574a8999713029b7a bk3.bin
8dccbad887dc112574a8999713029b7a bk4.bin
058bce361fd03ef3f9de2285dd12e5b4 a3403.bin
-------------------------------------------------------------------------------
sudo flashrom -p internal -w /home/a3403.bin -i bios --ifd --noverify-all
flashrom v1.2 on Linux 5.19.0-15-generic (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found chipset "Intel H170".
This chipset is marked as untested. If you are using an up-to-date version
of flashrom *and* were (not) able to successfully update your firmware with it,
then please email a report to flashrom@flashrom.org including a verbose (-V) log.
Thank you!
Enabling flash write... Warning: BIOS region SMM protection is enabled!
Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed.
New value is 0xaa.
SPI Configuration is locked down.
FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
FREG2: Management Engine region (0x00003000-0x0027ffff) is locked.
Not all flash regions are freely accessible by flashrom. This is most likely
due to an active ME. Please see https://flashrom.org/ME for details.
At least some flash regions are read protected. You have to use a flash
layout and include only accessible regions. For write operations, you'll
additionally need the --noverify-all switch. See manpage for more details.
Enabling hardware sequencing because some important opcode is locked.
PROBLEMS, continuing anyway
Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.
Reading ich descriptor... done.
Using region: "bios".
Reading old flash chip contents... done.
Erasing and writing flash chip... Transaction error between offset 0x00280000 and 0x00280fff (= 0x00280000 + 4095)!
Reading current flash chip contents... done. Looking for another erase function.
Looking for another erase function.
Looking for another erase function.
Looking for another erase function.
Looking for another erase function.
Looking for another erase function.
Looking for another erase function.
No usable erase functions left.
FAILED!
Uh oh. Erase/write failed.
Your flash chip is in an unknown state.
Get help on IRC at chat.freenode.net (channel #flashrom) or
mail flashrom@flashrom.org with the subject "FAILED: <your board name>"!
-------------------------------------------------------------------------------
DO NOT REBOOT OR POWEROFF!
root@kubuntu:/home#
https://x86sec.com/posts/2022/09/08/removing-intel-ME-on-x1-carbon/
Boot Kubuntu from USB drive.
sudo dmidecode -s bios-release-date
sudo dmidecode -s bios-revision
sudo dmidecode -s bios-vendor
sudo dmidecode -s bios-version
sudo apt install flashrom
-r dump1.bin => read chip and save content into file
-r dump2.bin
-r dump3.bin
md5sum dump1.bin dump2.bin dump3.bin
Hashes SHOULD BE identical.
-E => erase chip content
-w firmware.bin => write file content to chip
flashrom -p ch341a_spi -c GD25B128ACPIG -w firmware.bin
Current BIOS: H170-PRO-GAMING-ASUS-3403
https://www.asus.com/supportonly/h170_pro_gaming/helpdesk_bios/
Problem: BIOS is not displayed, can’t enter BIOS, cursor/underscore on black screen.
Cause: unknown. PC stayed some time unused and then this… Power on PC and it shows black screen with non-blinking cursor, then monitor blinks and you get same black screen with non-blinking cursor. Tried on old and new TFT monitors with DP, HDMI, VGA, DVI-D – same. Tried on discrete video – same.
Potential cause: low CMOS KTS battery - 2.6 V - may have corrupted BIOS.
I can boot from USB WinPE without any problems and see hardware with utilities, if no OS is installed on any HDD or SSD.
Windows PE => CMD with admin rights => shutdown /r /fw /f /t 0
I can boot from Win 10 USB and install Windows 10 on HDD or M.2 SSD, but after install Windows won’t boot. You get same black screen with non-blinking cursor.
I can’t enter BIOS by pressing F2 or Del, but Ctrl+Alt+Del reboots PC without problems.
When entering UEFI BIOS from Kubuntu USB GRUB menu PC turns off and then restarts.
I can’t flash BIOS with BUPDATER or AFUDOS.
With BUPDATER PC simply reboots or proposes to secure flash and reboots.
With AFUDOS I get message that BIOS is write protected. Can’t backup it and can’t flash it.
I changed battery, unplugged devices, removed CPU, tried another PSU, changed memory modules, reset CMOS many times but nothing helps. Looks like BIOS is working because with service utilities booted from USB drive I can see sensors, all specs, test video and cpu, hdd and ssd are visible, etc… But I can't enter BIOS.
BIOS chip flash solved the problem. Used buggy CH341A black USB 5V adapter, CH341-USB/CH341WDM.INF driver, UEFITool.exe, AsProgrammer_2.0.3a, Windows 7.
AFTER 3805 BIOS flash LAN Intel Ethernet Connection (2) I219-LM stopped working!!!
Flashed 3403 BIOS again!
Asus H170 PRO GAMING BIOS chip model: GigaDevice GD25B128CPIG E6S556 AH1644
https://winraid.level1techs.com/t/asus-h170-pro-bios-recovery/31530 - Asus H170 Pro BIOS recovery
https://www.youtube.com/watch?v=BYXKOo4sJqM - Прошивка bios программатором CH341 AsProgrammer под мутанта
https://www.youtube.com/watch?v=Z9IuCtNuakE - Прошивка BIOS программатором CH341A
https://www.youtube.com/watch?v=dpjs4-B7HPU - Взлом системы - моддим bios Z170 под CoffeLake
https://github.com/corna/me_cleaner/issues/98 - Flash Asus Z170 Pro Gaming using Ubuntu
https://www.cryptoprofi.info/?p=10901 - How to flash BIOS chips using RT809F programmer
https://greentechreviews.ru/2020/09/09/vosstanovlenie-bios-v-domashnih-i-okolo-togo-usloviyah/
https://www.wimsbios.com/amiflasher.jsp#gsc.tab=0
https://forums.overclockers.ru/viewtopic.php?f=1&t=23980&start=9260
https://i2hard.ru/publications/30697/
Install CH341A drivers and AsProgrammer_2.0.3a on Windows.
Install flashrom on Linux. [ You may also need libftdi1-2, libusb-0.1-4 ]
To convert an ASUS .CAP BIOS file into a .BIN file, follow one of these methods:
Method 1: Remove the CAP Header Manually (Hex Editor)
Open the .CAP file in a hex editor (e.g., HxD or Hex Editor Neo).
Look for the header size:
ASUS BIOS .CAP files often have a 2 KB (0x800) or 4 KB (0x1000) header. Check the first few bytes — if it starts with "AMI", "ASUS", or similar markers, it’s part of the header.
Delete the first 2 KB or 4 KB from the file.
Save the modified file as .BIN and use it for flashing.
Method 2: Extract with UEFITool
Download UEFITool (GitHub).
Open the .CAP file in UEFITool.
Right-click the BIOS region (usually labeled BIOS Region or UEFI Image).
Select "Extract as is" and save it as a .BIN file. This removes unnecessary headers while preserving all firmware regions.
Method 3: Use AMI Firmware Update Tools
Download AFUWIN or AFUDOS (AMI tools for BIOS modification).
afuwin.exe /CAP_TO_BIN input.CAP output.BIN
(Command may vary depending on your BIOS type.) This extracts the raw BIOS image.
After conversion, check that:
The .BIN file is slightly smaller than the .CAP file.
The structure is correct (compare it with an extracted .BIN from a working board).
It includes the necessary firmware regions (e.g., ME firmware for Intel chipsets).
Після зміни частоти памяті чи ввімкнення профілю XMP оперативної памяті, вентилятор процесора підвищив оберти і став шалено шуміти.
Змінивши профіль, перейдіть у Hardware Monitor і настройте криві кулера чи просто змініть до значень за замовчуванням, в даному випадку клавішею D.
Go to Control Panel Network Settings
1. Leave homegroup.
2. "See Full Map" in right upper corner to show network devices.
In VirtualBox go to Settings > Network > Attached to > Bridged Adapter.
ping 192.168.1.1
Reset network settings in cmd, if necessary:
ipconfig /release
ipconfig /renew
ipconfig /flushdns