registry modification requires a "sync" or "refresh" on the parent key.

opcode 0xb added to do this.  a likely candidate name is "RegFlushKey".
(This used to be commit 5e9567e3c7d4ee8624a448fcccfcd8003913dbbf)

1 files changed, 6 insertions, 0 deletions

diff --git a/source3/rpcclient/cmd_reg.c b/source3/rpcclient/cmd_reg.c
index 6430db2627..7c640a9a52 100644
--- a/source3/rpcclient/cmd_reg.c
+++ b/source3/rpcclient/cmd_reg.c
@@ -489,6 +489,9 @@ void cmd_reg_create_val(struct client_info *info)
 	res4 = res3 ? do_reg_create_val(smb_cli, &parent_pol,
 				 val_name, val_type, &value) : False;
 
+	/* some sort of "sync" or "refresh" on the parent key? */
+	res4 = res4 ? do_reg_unk_b(smb_cli, &parent_pol) : False;
+
 	/* close the val handle */
 	res3 = res3 ? do_reg_close(smb_cli, &parent_pol) : False;
 
@@ -571,6 +574,9 @@ void cmd_reg_create_key(struct client_info *info)
 	res4 = res3 ? do_reg_create_key(smb_cli, &parent_pol,
 				 key_name, key_class, &sam_access, &key_pol) : False;
 
+	/* some sort of "sync" or "refresh" on the parent key? */
+	res4 = res4 ? do_reg_unk_b(smb_cli, &parent_pol) : False;
+
 	/* close the key handle */
 	res4 = res4 ? do_reg_close(smb_cli, &key_pol) : False;