From 0839465eaed172e2958f0dca857f118dbff0f317 Mon Sep 17 00:00:00 2001 From: Derek Bruening Date: Fri, 19 Jan 2024 17:43:54 -0500 Subject: [PATCH] i#6570: Ignore bcrypt.dll init failure (#6571) A recent Windows update caused the bcrypt.dll process init routine to fail. This made the unit_tests and client.loader tests fail. For now we ignore the failure which so far has no harmful visible side effects. Fixes #6570 --- core/win32/loader.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/core/win32/loader.c b/core/win32/loader.c index 9acf13d1777..005ee062c8f 100644 --- a/core/win32/loader.c +++ b/core/win32/loader.c @@ -1,5 +1,5 @@ /* ********************************************************** - * Copyright (c) 2011-2021 Google, Inc. All rights reserved. + * Copyright (c) 2011-2024 Google, Inc. All rights reserved. * Copyright (c) 2009-2010 Derek Bruening All rights reserved. * **********************************************************/ @@ -1501,7 +1501,11 @@ privload_call_entry(dcontext_t *dcontext, privmod_t *privmod, uint reason) /* i#2221: combase's entry fails on win10. So far ignoring it * hasn't cause any problems with simple clients. */ - str_case_prefix(privmod->name, "combase"))) { + str_case_prefix(privmod->name, "combase") || + /* i#6570: bcrypt's entry suddenly started failing. Ignoring it + * is working so far; if that changes we'll have to dig into it. + */ + str_case_prefix(privmod->name, "bcrypt"))) { LOG(GLOBAL, LOG_LOADER, 1, "%s: ignoring failure of %s entry\n", __FUNCTION__, privmod->name); res = TRUE;