Unstoppable error windows popping up after slimming down Windows 10 LTSB 1067.

[MC_MuHyeon]

Hi. I slimmed down a Windows 10 LTSB Korean 1607 to my taste and after I install the modified OS to Virtualbox and log in as an administrator I get an error message saying (in korean):

the instruction 0x00007FFFD88B371A referenced memory at 0x00000....0000. the memory could not be written.

This error message window keeps popping up every time I close it. It doesn't stop appearing. What could be wrong? Below is the preset that I've used for tweaking my OS. Also I've integrated three update packages (kb4049065, kb4074595, kb4077525) prior to tweaking the OS image file.

The image below is the endless error message I get:

 

[nuhi]

Thanks, sorry for the delay, I did keep a few tabs open and forgot to recheck them.
Btw there is a high chance that version 6080 works fine, which has this change:
"MiracastView removal could cause a long lasting blank screen on logon after 1607 CU install"

If you already retried with 6080, let me know, no need to do it now as I will.

Trying, will reply back.

 

[MC_MuHyeon]

Thanks, sorry for the delay, I did keep a few tabs open and forgot to recheck them.
Btw there is a high chance that version 6080 works fine, which has this change:
"MiracastView removal could cause a long lasting blank screen on logon after 1607 CU install"

If you already retried with 6080, let me know, no need to do it now as I will.

Trying, will reply back.

Thank you for your answer. My NTLite version is 6080 and I tried the same thing and the message still appears.

 

[nuhi]

Tried on English and Chinese ISO, with those 3 KBs, no issue.

Will get Korean ISO (ko_windows_10_enterprise_2016_ltsb_x64_dvd_9057889.iso), do you know the exact ISO filename you're using? Asking because there are multiple versions if any of the updates was already pre-integrated.
In the meantime, did you use the "Clean updates" option when integrating that ISO with older version, which version was it do you know?
There should be Autosaved session in the root of it with the version info in it.
Or if you integrated manually/via a script, or not used update cleanup, then the issue is not there.


edit: tried on the mentioned Korean ISO as well, still no issue with the TaskHost, but the Start menu is not working so will check that tomorrow if it's just too much components removed or a component removes too much.
Btw I had to keep VMWare components to test on my VM, otherwise it was blue-screening. Just mentioning if when this start menu issue is solved, you may want to first test with VMWare compat kept so we are on the same page.

Thanks.

 

[MC_MuHyeon]

Tried on English and Chinese ISO, with those 3 KBs, no issue.

Will get Korean ISO (ko_windows_10_enterprise_2016_ltsb_x64_dvd_9057889.iso), do you know the exact ISO filename you're using? Asking because there are multiple versions if any of the updates was already pre-integrated.
In the meantime, did you use the "Clean updates" option when integrating that ISO with older version, which version was it do you know?
There should be Autosaved session in the root of it with the version info in it.
Or if you integrated manually/via a script, or not used update cleanup, then the issue is not there.


edit: tried on the mentioned Korean ISO as well, still no issue with the TaskHost, but the Start menu is not working so will check that tomorrow if it's just too much components removed or a component removes too much.
Btw I had to keep VMWare components to test on my VM, otherwise it was blue-screening. Just mentioning if when this start menu issue is solved, you may want to first test with VMWare compat kept so we are on the same page.

Thanks.

Yes the file name is "ko_windows_10_enterprise_2016_ltsb_x64_dvd_9057889.iso". There are no updates pre-applied to it. Just a Korean language pack. I tried slimming twice and in the first time I cleaned update backups with the second latest version of NTLite, and for the second time I cleaned update backups with the latest one (ver 6080).

I will tell the entire process that I've done to slim a Win 10. The process is same for my first (using second latest NTLite) and second (using the latest NTLite) trials.

Firstly I copied all component files in an iso file to a workable folder. Then I applied 3 updates for Win10 1607, which are KB4049065, KB4088785 (adobe flash player security update) and KB4088787 (cumulative update, not a delta update). I also imported drivers from my host PC. Then I finished the work on a install folder by applying updates and drivers. I did clean up update backups and reused driver cache. At the end of this process I didn't backup logs since there was nothing to modify but to add (updates and drivers).

I then made a copy of the new-made installer folder somewhere else (I didn't do update & driver addition and components removal simultaneously since if things go wrong I have to start again from applying updates and drivers) and did component removals, settings, unattended, etc. I finished the work with a session created. After I ran to the problem I've mentioned above I uploaded the session file. This is the end of my story.

No other 3rd party tweaking programs were used.

Thank you for your hard work, and I hope my answers will help you a bit.

Sincerely, MC_MuHyeon.

 

[nuhi]

OK, I had not reproduced your TaskHost issue.

But I have found that EventLog is breaking OOBE (meaning the setup loops if you don't autologon), you do autologon so it's invisible.
Might be related as the issue was a bit unexpected, so I made you a pre-release version with that fix.

The TaskHost issue also could be that your pre-patched iso was using old version update cleanup? I know you answered that to some extent but just to be clear, make sure to use the newer build from scratch (clean ISO).
In general when backing up pre-integrated ISO, please don't use removals or update cleanup, so those are always done by the latest version in case of fixes.

I have sent you the pre-release version link with EventLog removal fixed, please try with fresh ISO + updates + removals + test version + enable VMWare compatibility just in case we have the same comparison.

Btw if you ever don't use Autologon during setup, make sure to enable OOBE compatibility, gonna have to add a warning for that.

Let me know how it goes.
Thanks.

 

[MC_MuHyeon]

OK, I had not reproduced your TaskHost issue.

But I have found that EventLog is breaking OOBE (meaning the setup loops if you don't autologon), you do autologon so it's invisible.
Might be related as the issue was a bit unexpected, so I made you a pre-release version with that fix.

The TaskHost issue also could be that your pre-patched iso was using old version update cleanup? I know you answered that to some extent but just to be clear, make sure to use the newer build from scratch (clean ISO).
In general when backing up pre-integrated ISO, please don't use removals or update cleanup, so those are always done by the latest version in case of fixes.

I have sent you the pre-release version link with EventLog removal fixed, please try with fresh ISO + updates + removals + test version + enable VMWare compatibility just in case we have the same comparison.

Btw if you ever don't use Autologon during setup, make sure to enable OOBE compatibility, gonna have to add a warning for that.

Let me know how it goes.
Thanks.

Hi. I did everything as you said (test version you gave me & fresh iso & update, driver, removal at once & VMware test run) and there are no taskhost error messages anymore. I deeply thank you for your suggested solution. The taskbar also works perfectly, and the graphics & audio problems are also gone (refer to the previous post I've made: https://www.ntlite.com/community/index.php?threads/some-problems-with-graphics-and-audio.208/).

However, there is a very very trivial problem I have, which is that I have to type account names to get logged in. I apparently disabled it in settings section but don't know why it occurs. Anyway, it's a minor problem so I don't need it to be fixed, just letting you know that the problem exists.

Anyway thank you very much for your hard work and lots of effort to solve my problem. Have a nice day!

Sincerely, MC_MuHyeon

P.S I like your product and I plan to promote this cool stuff in Korean online communities (many Koreans also dislike Microsoft's way of making operating systems too). Do you mind my promoting your product? I won't take any monetary benefits if I do so.

Also want to mention that I was a bit harsh on you people when I urged you to solve my forgotten problems. I could've been more polite. I apologize for that.

 

[nuhi]

@MC_MuHyeon, thank you for confirming the fix.

This is the setting that makes it prompt user name: "Use classic logon"
"The classic logon screen requires users to manually enter a logon name and password to access a system. By default Windows displays usernames for selection."
You can change it by editing C:\Windows with the tool directly ("live mode").

Sure, you can promote the tool, just don't over-promise what it can do, nor insult Microsoft while doing so.

Thanks for the apology, but it's me who was slow at replying. From your perspective the report was ignored and I understand that.
I'll have added forum replying to my schedule, as I have had too big pauses the last month, I did work on the tool, but disconnected myself from the feedback for too long.

Keep me updated if anything comes up or you hear some bug being reported outside of my scope and language.
Appreciated.