try a more common image format

@glenn reupload in .jpeg.

ok, i can see the error. now to find out what is generating it.  can you post the log please, you'll probably need to zip it.

@glenn Here is my logs folder compressed in a .zip

this is a typical error entry in your log file:

Installing $0015
  Pack:     drivers\DP_Chipset_24090.7z
  Name:     PCI Express Root Port
  Provider: Advanced Micro Devices Inc.
  Date:     12/21/2023
  Version:  1.0.0.10
  HWID:     PCI\VEN_1022&DEV_14EF&SUBSYS_14531022&REV_00
  inf:      AMD\FORCED\PCIe\10x64\1.0.0.10\amdusb4pcifilter.inf,amd.ntamd64.10.0
  Score:    00FF0000

Extracting via 'app x -y "drivers\DP_Chipset_24090.7z" -o"C:\Users\hyp3r\AppData\Local\Temp\SDIO" "AMD\FORCED\PCIe\10x64\1.0.0.10\" "AMD\FORCED\USBhub\10x64\1.0.0.11\"'
Ret 0, 1 secs
Install32 'PCI\VEN_1022&DEV_14EF&SUBSYS_14531022&REV_00','C:\Users\hyp3r\AppData\Local\Temp\SDIO\AMD\FORCED\PCIe\10x64\1.0.0.10\amdusb4pcifilter.inf'
Dir: (C:\Users\hyp3r\AppData\Local\Temp\SDIO)
Created 'C:\Users\hyp3r\AppData\Local\Temp\SDIO\install64.exe'
Resize to 128->140
'C:\Users\hyp3r\AppData\Local\Temp\SDIO\install64.exe "PCI\VEN_1022&DEV_14EF&SUBSYS_14531022&REV_00" "C:\Users\hyp3r\AppData\Local\Temp\SDIO\AMD\FORCED\PCIe\10x64\1.0.0.10\amdusb4pcifilter.inf"'
Run(C:\Users\hyp3r\AppData\Local\Temp\SDIO\install64.exe,"PCI\VEN_1022&DEV_14EF&SUBSYS_14531022&REV_00" "C:\Users\hyp3r\AppData\Local\Temp\SDIO\AMD\FORCED\PCIe\10x64\1.0.0.10\amdusb4pcifilter.inf",0,1)
Ret 259(0x103),norb,0 secs

Everything is correct as it runs the installer. The installer returns 259(0x103) after 0 seconds. That particular return code has special meaning according to https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-getexitcodeprocess , and seems to indicate that the process being queried by GetExitCodeProcess is still active.  I don't know precisely to what process this refers. I will need to explore the install64.exe code to understand where the error originates. That's a job for next week.

it's not something like AV blocking it is it?

the code for install64.exe is really simple.

int WINAPI WinMain(HINSTANCE hThisInstance,HINSTANCE hPrevInstance,LPSTR lpszArgument,int nCmdShow)
{
	UNREFERENCED_PARAMETER(hThisInstance);
	UNREFERENCED_PARAMETER(hPrevInstance);
	UNREFERENCED_PARAMETER(lpszArgument);
	UNREFERENCED_PARAMETER(nCmdShow);

	WCHAR **argv;
    int argc;
    int ret=0,needreboot=0,lr;

	wprintf(L"Start\n");
	wprintf(L"Command: '%s'\n",GetCommandLineW());
    argv=CommandLineToArgvW(GetCommandLineW(),&argc);

	if(argc==3)
	{
		wprintf(L"Install64.exe '%s' '%s'\n",argv[1],argv[2]);
		ret=UpdateDriverForPlugAndPlayDevices(FindWindow(L"classSDIMain",0),argv[1],argv[2],INSTALLFLAG_FORCE,&needreboot);
	}
	else
		printf("argc=%d\n",argc);
	lr=GetLastError();
	wprintf(L"Finished %d,%d,%d(%X)\n",ret,needreboot,lr,lr);
	if(!ret)
	{
		ret=lr;
		print_error(lr,L"");
	}

	LocalFree(argv);
	if(!ret)return lr;
	return ret+(needreboot?0x80000000:0);
}

It makes a call to the Windows API function UpdateDriverForPlugAndPlayDevices.

https://learn.microsoft.com/en-us/windows/win32/api/newdev/nf-newdev-updatedriverforplugandplaydevicesa

If this function reports an error, it retrieves the error code using the standard GetLastError. This error code is then returned to SDIO.

According to the above Microsoft page, UpdateDriverForPlugAndPlayDevices will return error 259 if:

The function found a match for the HardwareId value, but the specified driver was not a better match than the current driver and the caller did not specify the INSTALLFLAG_FORCE flag.

However as you can see from the code above, the INSTALLFLAG_FORCE is specified.

There is a discussion on this topic here https://stackoverflow.com/questions/11474317/updatedriverforplugandplaydevices-error-is-telling-me-im-not-doing-something . In this case the issue was with the INF file. Is it possible all of the INF files are faulty somehow?

I'm not sure where that leaves us.  I'd be interested to know the outcome if you were to manually uninstall whatever drivers are currently installed before running SDIO again.

@glenn Hello glenn, I'm really hoping you can help. I'm wondering if you can provide some further steps to diagnosing this issue. I'm having the same exact problem as OP. Attached are some screenshots.

I've tried uninstalling and reinstalling drivers in normal mode and safe mode, tried getting these chipset drivers directly from AMD and also directly from ASUS. I've been experiencing this very same "error 103" issue for around 3-4 months and around 2 months ago I did a clean reinstallation of Windows 11 and when running SDIO the same issue persisted between clean reinstallations of Windows 11. The worst part is I think it could be the answer to all the strange little stuttering/glitching problems I have with my laptop since at this point it seems like I've ruled out everything else. In one of the screenshots where you can see driver details, you see instead of AMD's Chipset driver it says they're using Microsoft's dated 2006 and under the device with the error 103 install issue is what appears to be peripherals connected to my system through USB.

Edit: Here's link to photo album <a href=" removed link " target="_blank" rel="noopener"> removed link

No ideas I'm afraid other than make sure you have a full compliment of OEM drivers for the exact model. Try putting Win10 on instead of Win11.