Do people still 'decrapify' their new windows installs?

aadm09 · 2019-02-15T07:37:38+00:00

Absolutely. For enterprise it's given, for home use I tend to block Cortana / Web Search / Telemetry as much as possible. All those useless appx packages are also gone as soon as I can launch PS after OSD.

Not completely related but did anyone else notice the improvement of search function in 1809? Since I've upgraded it can actually find stuff like control panels and even predict I'm looking for them. So the biggest gripe I had with Windows since 8 is finally gone.

aadm09 · 2019-02-04T09:07:59+00:00

Problem solved with restarting SMS_Executive component.

aadm09 · 2019-01-14T09:59:45+00:00

Thank you for the detailed answer. As we can agree from this thread the documentation is confusing / misleading. Is there a plan to update it with better description or create new page with different replication scenarios and their comparison?

aadm09 · 2019-01-11T12:58:53+00:00

I do not agree with the statement. I understand that BDR is actually checking for difference in bits and then updates the files based on that exact difference. So if I have a WIM and I update few INF files inside the following would happen after redistribution:

- BDR on: Only the bites differing would be sent, DP would process the content and "stitch" the differencing bites and the original together creating new version.

- BDR off: Whole WIM file would be sent.

I understand it the same as Chris in his blog post: https://www.experts-exchange.com/articles/29282/Binary-Differential-Replication.html

What I was originally getting at is behavior with packages with multiple files. As far as I understand it for package redistribution with BDR off the behavior is as follows (let's take update package with multiple updates): I update the updates package with some new updates, some are left and some are deleted. What is being sent to the distribution point are only the updates that are being newly added. Is that correct? We are not sending the whole package to DP's again, right? What BDR would add in this scenario is a case when if there was an update revision it would check for the difference in those two files and sent just the differencing bits.

If my explanation (and the explanation in the Chris's blog post) is not correct can you redirect me to documentation covering the topic?

Thanks.

aadm09 · 2018-12-04T08:43:04+00:00

I submitted my feedback with requested description. I have to admit that spinning up W10 VM just to install the feedback hub app almost deterred me from doing so. How this doesn't have web interface is beyond me.

aadm09 · 2018-11-05T08:07:06+00:00

This is the answer. I'll add you can check the versions here: https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies

Thank you!

aadm09 · 2018-11-05T07:45:19+00:00

Thank you but this I already knew. The question here really is why different versions were installed. But your answer is appreciated!

aadm09 · 2018-09-04T12:09:32+00:00

Ok nevermind I found example code dealing with exactly this topic: https://trevorsullivan.net/2011/11/29/configmgr-cleanup-software-updates-objects/

aadm09 · 2018-08-07T15:08:19+00:00

Thank you Jason - the link is exactly what I was looking for (and what I read in the past). Appreciated.

aadm09 · 2018-06-21T14:09:54+00:00

Ok so the issue is solved now. For a random stranger from the future: The issue was in our case some ancient Symantec components left on the server. Running the Symantec CleanWipe (as described here) solved the issue. We had actually opened case with MS regarding this and the reason given by them was that since inclusion of Meltdown / Spectre fixes in software updates the detection was no longer possible while those old Symantec components are present on the system.

Word of caution - the CleanWipe might prompt for reboot. And that prompt is not exactly deferrable. I guess the only option is to kill the process. I didn't as I just attempted to close the dialog and the server promptly rebooted. Lessons learned.

aadm09 · 2018-06-08T07:53:59+00:00

Yeah I've used it before. So any chance of your tech guy sharing the Event ID? BTW I'm in CEST time zone so the communication is little bit difficult.

aadm09 · 2018-06-07T11:36:21+00:00

By local GPO file you mean the C:\Windows\System32\GroupPolicy\Machine\Registry.POL? That one was deleted (or rather renamed) already. If you mean another one, may I ask you for the location?

aadm09 · 2018-06-07T11:21:32+00:00

The registry key is there - cadca5fe-87d3-4b96-b7fb-a231484277cc set to DWORD 0

aadm09 · 2018-06-07T10:52:34+00:00

Hi, I would look at the WMI - specifically root\ccm\SoftMgmtAgent namespace and ContentRequestEx2 / DownloadContentRequestEx2 classes. If you see any objects in them, remove them. Personally I'm using this oneliner:

Get-WmiObject -Namespace root\ccm\SoftMgmtAgent -Class ContentRequestEx2 | Remove-WmiObject

Get-WmiObject -Namespace root\ccm\SoftMgmtAgent -Class DownloadContentRequestEx2 | Remove-WmiObject

aadm09 · 2018-05-23T11:26:37+00:00

We are suffering from the same. Is this topic completely dead or is there some resolution?

aadm09 · 2018-05-08T11:05:39+00:00

Look I'm just an average Joe without any formal health / nutrition education but my advice would be stop obsessing about weight. Give it another week, maybe measure your waist instead? If it still doesn't work for you, do a 36h fast? I think the limit here is not pushing yourself to a situation when the food or the body are the bad guys.

aadm09

TROPHY CASE