Windows is not activating

qou

Member
"Something prevented us from communicating with our activation server - 0xc0020036
 

Attachments

  • autosaved.xml
    90.7 KB
Too many services are disabled:
At least could be BITS, WU & OS and OneSync disabled in Features.
 
I switched back most of the disabled services , and theres nothing about OneSync in Features
 
I switched back most of the disabled services , and theres nothing about OneSync in Features
Don't know the feature name as I'm working with 7 but in your preset this is related:
Code:
<Feature name="OneCoreUAP.OneSync~~~~0.0.1.0">false</Feature>

Have You tested after resetting the services to default?
 
I switched back most of the disabled services , and theres nothing about OneSync in Features
To add to what Kasual said.

Please try with no service configured for a confirmation. Services dependency is a Windows question, there is nothing in removals with Activation protection that can break server connection as reported in the error, that we know of.

However, if you get the same with the services on default (starting fresh, not just after install, setup might be broken if services were disabled directly on the image), then please attach the preset demonstrating the issue.
If you ever find exactly which service was it, I'm interested to add a warning or a lock.

Thanks.
 
Hello
I've made new iso with the same preset, this time I switched back to default most of the extra services(I don;t know if this what fixed the problem) but now it works, I'm attaching the current preset after the extra services change if it will help to compare with the preset on the first post.
 

Attachments

  • Autosavedsession.xml
    85 KB
Thanks qou, will be reviewing the diff and see if anything can be extracted.
There are some extra custom things in there as well which may skew the results, will try only services.
 
Comparing the before and after, my guess is this bad boy.
powershell -Command Set-NetFirewallProfile -DefaultOutboundAction Block

There's no activation key in the preset, which could avoid this problem since activation would finish before Post-setup runs.
 
after looking at the preset, it is from that LTSC v1.0.5c file and ive experienced the same thing and this post setup option that garlin points to is the cause, with it set ive not been even able to connect to the internet let alone activate windows in the past, the presets need to be gone over and updated for more recent versions, as ive used alot of this preset pack in my experiments and it would be very helpful to have this same fella redo that preset pack
 
-DefaultOutboundAction Block is paranoid, it stops all outbound traffic unless allow rules exist.
 
its got alot of mighty fine tweaks and presets in that pack, its just so many errors, i messed around alot with this pack of presets when I first started with nt lite
 
one other thing you got to take into account is that it was built for LTSC 1809 only so using any of it on later builds may not work or it may screw them up. my rule is to treat each w10 build series as an OS in its own right, you might be ok with the next higher build series, ie 1903, 1909 at a stretch maybe, but i wouldnt use it asis on 20builds upwards. you'd have to test test test and cherry pick.
 
Comparing the before and after, my guess is this bad boy.


There's no activation key in the preset, which could avoid this problem since activation would finish before Post-setup runs.
Nah, I've disabled that straight after installation. Also tried with the whole firewall setup cut from post-install scripts, no change in behavior.
 
one other thing you got to take into account is that it was built for LTSC 1809 only so using any of it on later builds may not work or it may screw them up. my rule is to treat each w10 build series as an OS in its own right, you might be ok with the next higher build series, ie 1903, 1909 at a stretch maybe, but i wouldnt use it asis on 20builds upwards. you'd have to test test test and cherry pick.
Yup, I'm applying that to the latest available Windows 10 LTSC.
 
extreme presets(including my own) can be a bloody menace in the wrong hands and even cause havoc in the right hands :(
i think they do more harm than good.
 
Back
Top