New
#1331
@JOKER77
The world of developers is divided into 2 categories.
The first, those who feel superior, who are succeptible, and who hide the bugs of their programs (when they really program): certainly the most numerous.
The second, those who know how to remain humble in any situation because they know that they are wrong, that they can still be wrong and make bugs in their programs.
I've been part of the second part since I started debugging "MSDOS2.0". I'm too old to change my mindset.
@Kyhi
Thank you for the explanations about MTPHelper. Our friend Slore is very active in his forum and ensures the maintenance of this driver.
@doudii
Bravo for the round corners
hi @doudiii
very thanx
finally
Here is Winpe 11 wearing his original attire
I hope this does not anger Microsoft
- - - Updated - - -
My previous reply was urgent so I put a few more I want to say
There is no person who does not make mistakes except the person who does not work. I greatly appreciate the research you are doing on Windows PE
pm has been running. I am honored to benefit from your information and research
Sorry for not getting back to you. 112mb was the size of the iso, but the iso folder was 2.? gb.
I continually recreate the error, either that or the iso is the right size but wont boot.
I was successful a few weeks ago in creating a good iso but I am struggling now.
I have downloaded the latest W10XPE and used fido to downloaded 19041.264 and 22621.525
has anyone been able to browse local network or directly type a remote share and connect?
only net use is working for me in latest release WinXPE and windows 11 22621
I can confirm that accessing \\servername\sharename ist not working with 22621. It seems like nothing happens at all, and after waitung for about 60 seconds I run into a cannot access type error message.
- - - Updated - - -
I am searching help on integrating the latest Veeam Agent 6 into WinXPE. It would be perfectly fine to run the installer from within WINXPE. This works perfectly btw without any error, but although the service is running, neither the GUI or TRAY Icon do show up properly. Running the File Level Recovery Tool manually seems to work, but at the very final step of the process, the tool cant communicate with the service and fails. It would be very cool to be able to recover individual files or folders from Veeam backups from within PE. A bare metal recovery can be done with the veeam recovery environment (also PE based), but a file level recovery requires the installation of the veeam agent on any Windows machine. I checked the creation process of the veeam recovery iso creation, and tried to adjust this for WINXPE, but failed. I am just not smart enough.... .
The veeam agent is free of charge but requires a registration to download, so I uploaded to belows share:
Schicks Digital!
Any help is appretiated.
@bigbadmoshe
for the fun...Only for the fun...
I read in my "traitement.ps1" file that you can see here :My new scripts and PDF - Page 2 - TheOven.org
affichage "=====>>>>>Modification de MiniNT dans Windows.UI.CredDialogController.dll"
$chMiniNt = "MiniNT"
$bytes = $srcencoding.GetBytes($chMiniNt)
$uMiniNt = [System.Text.Encoding]::Convert($srcencoding, $dstencoding, $bytes)
$Sign = $uMiniNt.clone()
$NewSign = $uMiniNt.clone()
$NewSign[0] = 78 #N
"Windows.UI.CredDialogController.dll" |foreach {
$file = join-path $MountSystem32 $_
if ( ! (test-path ("$file.org")) ) {Copy-Item ("$file") ("$file.org")}
set-ownerForFile "$file" "none"
$nb=$typeReplaceInFile[0]::ReplaceInFile($file,$file,$Sign,$NewSign)
affichage "`tnb signatures : $nb"
}some details : change MININT by NININT in Windows.UI.CredDialogController.dllX:\Windows\System32>fc Windows.UI.CredDialogController.dll Windows.UI.CredDialogController.dll.org
Comparaison des fichiers Windows.UI.CredDialogController.dll et WINDOWS.UI.CREDDIALOGCONTROLLER.DLL.ORG
***** Windows.UI.CredDialogController.dll
\
N
i
***** WINDOWS.UI.CREDDIALOGCONTROLLER.DLL.ORG
\
M
i
*****
It works for me for a long time.
Noel
i say : " change MININT by NININT in Windows.UI.CredDialogController.dll"
it's true that I don't use the Win10XPE project.
Also it may be that some files or keys are missing in this project.
But with this simple modification the connection with the Explorer GUI works in my Winpe 11 22h2
Maybe you can edit a byte in this file and do a test.
I can't remember since Winpe's version this simple modification works.
If you are unable to make the change, please forget my intervention.