Save this as cmd file, and run. Code: @echo off (cd /d "%~dp0")&&(NET FILE||(powershell start-process -FilePath '%0' -verb runas)&&(exit /B)) >NUL 2>&1 SET UserToRemove="defaultuser0" REM 'CALL' check registry subroutine check for existance and remove. FOR /f "tokens=*" %%a IN ('REG query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList"^|find /i "s-1-5-21"') DO CALL :ChkRegistry "%%a" GOTO :Finish :ChkRegistry REM ----------------------------------------------------------------------- REM Results of ERRORLEVEL are: REM 0 -- If UserToRemove is found in the registry then run rest of script. REM 1 -- If UserToRemove is NOT found in the registry then exit script. REM ----------------------------------------------------------------------- FOR /f "tokens=3" %%g in ('reg query %1 /v ProfileImagePath') DO SET UserProfilePath=%%g FOR /f "tokens=3 delims=\" %%e in ('echo %UserProfilePath%') DO SET ProfileName=%%e FOR /f "tokens=1 delims=." %%f IN ('echo %ProfileName%') DO SET ParseRegistry=%%f ECHO %UserToRemove%|find /I "%ParseRegistry%" > NUL IF ERRORLEVEL=1 GOTO :Finish REM Remove that user... RMDIR "%SystemDrive%\Users\%ProfileName%" /s /q REG delete %1 /f >nul IF EXIST "%SystemDrive%\Users\%ProfileName%" GOTO :RetryDirRemove GOTO :Finish :RetryDirRemove TAKEOWN /F "%ProfileName%" >nul TIMEOUT /T 2 >nul ICACLS "%ProfileName%" /GRANT *S-1-1-0:F >nul TIMEOUT /T 2 >nul RMDIR "%SystemDrive%\Users\%ProfileName%" /s /q :Finish REM End of script...
No truthfully I didn't. I find lots of code, and save it. It has been a long time since I used it, or had to.
Thought it was just me. Two days ago the profile went south, after booting from USB hdd to PE, sure enough, default0 was there. Cheers.
1) Copy the windows10.0-KB4093112-x64.cab or windows10.0-KB4093112-x64.msu to <Packs\WHD\w10\x64\Cumulative> folder and then use the ToolKit's Integrate WHD Update Pack->Integrate WHD General Updates. or 2) Copy the windows10.0-KB4093112-x64.cab or windows10.0-KB4093112-x64.msu to <Updates\w10\x64> folder and then use the ToolKit's Integrate Windows Updates->Integrate Windows Updates.
The ToolKit component removal for components like Defender, Smartscreen, PeopleExperienceHost which uses the ToolKitHelper.exe method is not yet updated for RS4. The previous RS3 list for removal will not be the same for RS4 and so it requires a lot for time for me to prepare the list of files/folders/registry/xml entries needed to be removed for RS4 for all languages and editions. The menu for Defender, SmartScreen and PeopleExeprienceHost is left intact and it will be functional once the code for removal is ready. Moreover, the MS has demoted the Windows 10 RS4 17133 from RTM Status and still there's a confusion what will be the actual RTM/GA build and then again I'll have update the whole ToolKit for the new build. So, It's better to wait for the proper RS4 RTM build to be released.
Nothing has broken for current RS4 build as of now, just wait for the correct RS4 build to be released.
I'ts not right for me to rush you, and im not but i'd like to ask what's a realistic timeframe for rs4 toolkit? need to plan on whether to stay on rs3 or not
Not Working: - Convert Edition. - Integrate Metro Apps. - Integrate WinPE Language Packages. - Remove Windows Components using ToolKitHelper.exe method (Defender, SmartScreen, PeopleExperienceHost).