[DISCUSSION] Windows 10 Demoted Back to Insider Preview 17133.1 (PC) [RS4_Release]

Mine still has no update

 

yep this process is clear as water

 

You need to login to view this posts content.

 

I know what it is and I want to delete it.

 

Today I've upgraded to Windows10, RS4(1803).
The brightness adjustment feature is not working.
Windows running with full brightness.

Any idea or solution?

 

@Enthousiast did you test the ESD ?
about the "problem" detecting the integrated serial key...
the ESD I downloaded was taken from this topic, on the Pastebin file, this one: 17133.1.180323-1312.rs4_release_clientconsumer_ret_x64fre_it-it

 

already answered this issue, take a look at some earlier post of mine

 

But I still see uknown driver. When I make clean install of Windows I see it too. It's look like the system want it (the driver).

 

So get the VID & PID Hardware ID, Google them and then leech the driver.

 

I don't understand you.

 

OK, take it back a step. Google 'what is vid and pid' and then read about how to get them. Once obtained, Google the VID & PID to find your driver and then install it. At a guess it's probably some stupid Intel Management Engine driver or similar.

 

Or you could just use a simple powershell script in the same folder as the esd file:
$ESDFilePath=Get-ChildItem *.esd
$ImageExclusions=@('Windows Setup Media','Microsoft Windows PE (x64)','Microsoft Windows Setup (x64)','Microsoft Windows PE (x86)','Microsoft Windows Setup (x86)')
$AllImages=Get-WindowsImage -ImagePath $ESDFilePath
write-host $AllImages.ImageName
$SetupMediaImage=$AllImages.Where({$_.ImageName -eq "Windows Setup Media"})
$SetupImage=$AllImages.Where({$_.ImageName -eq "Microsoft Windows Setup (x64)" -or $_.ImageName -eq "Microsoft Windows Setup (x86)"})
New-Item -Path ".\ISOFiles" -ItemType Directory -ErrorAction SilentlyContinue
Expand-WindowsImage -ImagePath $ESDFilePath -Index $SetupMediaImage.ImageIndex -ApplyPath ".\ISOFiles"
Export-WindowsImage -SourceImagePath $ESDFilePath -SourceIndex $SetupImage.ImageIndex -CompressionType Maximum -DestinationImagePath ".\ISOFiles\Sources\boot.wim" -DestinationName $SetupImage.ImageName
$AllImages.Where({$_.ImageName -notin $ImageExclusions}).foreach( {
Export-WindowsImage -SourceImagePath $ESDFilePath -SourceIndex $_.ImageIndex -CompressionType Maximum -DestinationImagePath ".\ISOFiles\Sources\Install.wim" -DestinationName $_.ImageName
} )

Will create the ISOFiles subdirectory that you can simply run setup from or copy over to a usb stick / make an iso out of it.

Edit: oops I had this on queue to submit and more posts have been added hence it looks out of place

 

Is there anyone using Visual Studio 2017 for C++ development on this build? I failed to build some libraries.. I'm not sure if it was the RS4 or something else.

Edit: Everything are fine now. The causes of the problem was not this build of RS4.

 

Yes. It's Intel Management Engine that installed when I install Intel Desktop Utilities that make BSOD. For what I need Intel Management Engine ?

 

You need to login to view this posts content.

 

Nobody can tell you why YOU need something. Only you can answer that question.

The bottom line is you're trying to install low level 3rd party software onto a version of Windows 10 that hasn't been released to the general public yet. My advice would be to ignore the unknown driver or disable it in Device Manager and then wait for Intel to update their software to support 1803. If that's unacceptable then feel free to hit up the recovery options in Settings and then roll back your version (if you upgraded). If it was a clean install then you'll need to find something else to obsess over for a week or two

 

You need to login to view this posts content.

 

Quoting myself here: Seems like it is not a Windows issue. Rocket League had a big update and their forums and reddit is full of this issue. Seems like they screwed some things up, so yeah taking this back